From 2731e3ab38c7b354a08023da04f62f923ac6192f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 21 Sep 2022 16:13:08 -0400 Subject: [PATCH] wording --- .../comment_4_ac9c166c2b0c3aad8391abb56654ecf2._comment | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/bugs/reports_file___34__modified__34___whenever_it_is_not/comment_4_ac9c166c2b0c3aad8391abb56654ecf2._comment b/doc/bugs/reports_file___34__modified__34___whenever_it_is_not/comment_4_ac9c166c2b0c3aad8391abb56654ecf2._comment index d4cfce6fbc..30e9d721ac 100644 --- a/doc/bugs/reports_file___34__modified__34___whenever_it_is_not/comment_4_ac9c166c2b0c3aad8391abb56654ecf2._comment +++ b/doc/bugs/reports_file___34__modified__34___whenever_it_is_not/comment_4_ac9c166c2b0c3aad8391abb56654ecf2._comment @@ -13,9 +13,9 @@ I expect that running `git update-index --refresh .dandi/assets.json` will fix git status. Can you confirm? The only way I know of that this can happen without the message is if a -drop or a get is still running, or gets interrupted after it -gets an unlocked file, but before it finishes. One of the last things -git-annex does is restage the unlocked files. +drop or a get is still running, or gets interrupted. One of the last things +git-annex before exiting is restage all the unlocked files that it has +updated. Short of that, it seems like it would have to be a bug that prevents restagePointerFile from working. Which might not be a bug in git-annex,