From 1a8087ace5a47aa5ac0d626801dcbd86b1c0ff3d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 2 Mar 2020 14:58:31 -0400 Subject: [PATCH] respond and close --- .../git-annex-fsck_reports_dead_keys_as_errors.mdwn | 1 + ...ment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment | 13 +++++++++++++ 2 files changed, 14 insertions(+) create mode 100644 doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment diff --git a/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn index 6bbc7532a5..9ae5f7899e 100644 --- a/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn +++ b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn @@ -51,3 +51,4 @@ git-annex: fsck: 1 failed ### 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) git-annex helps me keep my sanity :) +> [[notabug|done]] per comments --[[Joey]] diff --git a/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment new file mode 100644 index 0000000000..f77fb1447a --- /dev/null +++ b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2020-03-02T18:54:05Z" + content=""" +As yes, I missed that you also had an example of fsck --key as well as fsck +of a file in the working tree with a dead key. + +I think the same basic reasoning applies for fsck --key as for fscking a +worktree file. The user appears to be particularly interested in that key, +so fsck should tell them about the obious problem that it has no remaining +content. It's not like --all. +"""]]