From: Joey Hess Date: Fri, 29 Jan 2021 16:53:57 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~98^2~131 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=7f6e2da321394cb8b0bcf21d59fdadfa71382215;p=git-annex.git comment --- diff --git a/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_3_05f178a19b8949efc5c6e189ff8fa5e0._comment b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_3_05f178a19b8949efc5c6e189ff8fa5e0._comment new file mode 100644 index 0000000000..d37c419fe4 --- /dev/null +++ b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_3_05f178a19b8949efc5c6e189ff8fa5e0._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-01-29T16:52:47Z" + content=""" +I've never seen this behavior, but it seems that if git thinks the files +are modified, either `git diff` or `git diff --cached` must show some kind +of change, and seeing what that change might be would be a useful clue to +what happened. +"""]]