followup and close
This commit is contained in:
parent
3953c7a0ce
commit
2e702960ab
2 changed files with 22 additions and 0 deletions
|
@ -34,3 +34,5 @@ $/usr/bin/sw_vers
|
|||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||
|
||||
Still rock solid maintaining the .dmgs and .pkgs for a 67GB [Munki](https://www.munki.org) repository.
|
||||
|
||||
> [[done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,20 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2020-07-25T16:09:17Z"
|
||||
content="""
|
||||
This is a near duplicate of a bug you filed before. I'm dubious about the
|
||||
value of these bug reports. As I said before:
|
||||
|
||||
The build version being a little behind is not uncommon when the
|
||||
autobuilder has not been keeping up for whatever reason. I generally don't
|
||||
block releases on autobuilds if it's the fault of the autobuilder and not
|
||||
a bug in git-annex's build process or test suite, and just ship the latest
|
||||
available build.
|
||||
|
||||
But maybe I'm missing something about how problimatic the build being
|
||||
slightly behind until the next release is for you?
|
||||
|
||||
The autobuilder has since caught up again, so the daily
|
||||
build is current.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue