summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-06-09 15:01:11 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-06-09 15:01:11 -0400
commit7d403a4f49c2c99b4e14a95cb3d0974fe9d1bd59 (patch)
treec5775cbc207bb542f4f0e639d80b3089f4b9e80f /doc
parent47c2ad33d08bb828cd63544bc4c9cb1d294fc090 (diff)
fixed
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/fsck_reports_unsolvable_problem.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/fsck_reports_unsolvable_problem.mdwn b/doc/bugs/fsck_reports_unsolvable_problem.mdwn
index d0164f8bc..56c794422 100644
--- a/doc/bugs/fsck_reports_unsolvable_problem.mdwn
+++ b/doc/bugs/fsck_reports_unsolvable_problem.mdwn
@@ -18,3 +18,10 @@ According to IRC this "can happen if you annexed a file and then deleted it with
5.20140717 from Ubuntu utopic
[[!tag confirmed]]
+
+> [[done]] -- fsck --all or in a bare repo will skip over keys that have
+> been marked dead, which can be done with `git annex dead --key`.
+>
+> Might go further later, and make `git annex drop --force`, when removing
+> the last copy of a key, mark it as dead. But maybe that is too DWIM.
+> --[[Joey]]