summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-05-01 14:18:02 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-05-01 14:20:05 -0400
commit99fff199b8d8556684de4c5767c091bf11850731 (patch)
tree98b7661d2a00958210d5022e92c5f7747f74ff69
parentfceb72b6db9503e6638550d41d2506cfd7b5a110 (diff)
closing; no followup and not clearly a bug
-rw-r--r--doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn3
-rw-r--r--doc/bugs/Repository_Information_Is_Lost.mdwn6
2 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn b/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn
index 7087247f5..eef705e69 100644
--- a/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn
+++ b/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn
@@ -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]]
diff --git a/doc/bugs/Repository_Information_Is_Lost.mdwn b/doc/bugs/Repository_Information_Is_Lost.mdwn
index 7b11ac4cf..cbaf866c8 100644
--- a/doc/bugs/Repository_Information_Is_Lost.mdwn
+++ b/doc/bugs/Repository_Information_Is_Lost.mdwn
@@ -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]]