From 5b659cebc4927daf5c0d7b210e55864a22564aac Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 28 Feb 2020 18:44:21 +0000 Subject: [PATCH] Added a comment: fsck of dead keys --- .../comment_3_99f2e030519d4fd6351fabb20c0c5f10._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_3_99f2e030519d4fd6351fabb20c0c5f10._comment diff --git a/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_3_99f2e030519d4fd6351fabb20c0c5f10._comment b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_3_99f2e030519d4fd6351fabb20c0c5f10._comment new file mode 100644 index 0000000000..12d3f64947 --- /dev/null +++ b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_3_99f2e030519d4fd6351fabb20c0c5f10._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="fsck of dead keys" + date="2020-02-28T18:44:21Z" + content=""" +\"having a file in your working tree whose content is missing is something that it's reasonable for fsck to mention as a problem\" -- makes sense. For [[`git-annex-fsck --key`|git-annex-fsck]], not sure you need to warn about an explicitly [[`git-annex-dead`|git-annex-dead]]'ed key, but I guess that depends on the context in which the command is used. +"""]]