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 (file)
index 0000000..d37c419
--- /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.
+"""]]