closing; no followup and not clearly a bug
This commit is contained in:
parent
6b6f9bcf1b
commit
25d3a7995c
2 changed files with 9 additions and 0 deletions
|
@ -1,3 +1,6 @@
|
|||
I recently had my git-annex repository die and it needed to be repaired. Two of my repositories are external hard drives. When I tried to use git-annex repair, it would churn for some hours, then error because the external hard drives were not plugged in. When I brought the two hard drives home from the various places that they are (safely) stored, it all worked fine, but it would have been great if git-annex repair could somehow do what it could with what was connected and do the rest as and when the other drives are plugged in. This must only become more of a problem as git-annex is used for longer, as one may have a handful of USB keys storing a little on each.
|
||||
|
||||
[[!taglink moreinfo]]
|
||||
|
||||
> With the lack of an error message or any followup, it's hard to take
|
||||
> this bug seriously, so [[done]] --[[Joey]]
|
||||
|
|
|
@ -31,3 +31,9 @@ Clones of my repositories lost all track of other repositories they only seem to
|
|||
"""]]
|
||||
|
||||
[[!tag moreinfo]]
|
||||
|
||||
> No followup for over a year, and not enough information in the intial
|
||||
> report to know if there's a bug at all. It occurs to me that the user
|
||||
> might have just forgotten to push the git-annex branch to wherever they
|
||||
> later cloned the repo from. `git annex sync` would fix that mistake up.
|
||||
> Anyway, [[done]]. --[[Joey]]
|
||||
|
|
Loading…
Add table
Reference in a new issue