From 70d11a209d8fb563989760fcd9e7a6d2f897b590 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 23 Oct 2023 13:46:46 -0400 Subject: [PATCH] notabug --- ...s_ok_for_a_file_that_is_not_in_the_remote.mdwn | 2 ++ ...nt_3_264a1b39c1677545af4c02901dd23d22._comment | 15 +++++++++++++++ 2 files changed, 17 insertions(+) create mode 100644 doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote/comment_3_264a1b39c1677545af4c02901dd23d22._comment diff --git a/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote.mdwn b/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote.mdwn index e29845fefa..a8d249d324 100644 --- a/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote.mdwn +++ b/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote.mdwn @@ -43,3 +43,5 @@ macOS """]] ### 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) + +> [[notabug|done]] --[[Joey]] diff --git a/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote/comment_3_264a1b39c1677545af4c02901dd23d22._comment b/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote/comment_3_264a1b39c1677545af4c02901dd23d22._comment new file mode 100644 index 0000000000..ba110ba0b5 --- /dev/null +++ b/doc/bugs/fsck_says_ok_for_a_file_that_is_not_in_the_remote/comment_3_264a1b39c1677545af4c02901dd23d22._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2023-10-23T17:41:04Z" + content=""" +Well `fsck --from` does check the consistency of what's in the remote. +That entails verifying that the remote contains the data that +git-annex thinks it contains. But it also means verifying that the remote +does not contain any data that git-annex didn't know it contains. + +Checking the file is not present on the remote is part of the latter. + +If you wanted to only verify that files git-annex thinks are on the remote +are present there, you could use eg `git-annex fsck --from theremote --in theremote` +"""]]