From 9750deafe790b1d92f5f185bf804494d01d3e2ad Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 2 Jun 2022 11:57:24 -0400 Subject: [PATCH] comment --- ..._8a355d509fb2005cfd9da8f2d4bb560e._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_10_8a355d509fb2005cfd9da8f2d4bb560e._comment diff --git a/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_10_8a355d509fb2005cfd9da8f2d4bb560e._comment b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_10_8a355d509fb2005cfd9da8f2d4bb560e._comment new file mode 100644 index 0000000000..96a850759b --- /dev/null +++ b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_10_8a355d509fb2005cfd9da8f2d4bb560e._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 10""" + date="2022-06-02T15:47:14Z" + content=""" +Well, I can confirm that, with .git/info/attributes missing, `git status` +displays unlocked files as modified. + +But, the bug originally reported here had the files only start to show up +as modified after some amount of time, not immediately. And also, it had +`git diff --cached` outputting nothing when run on those files. The +behavior with .git/info/attributes does not match either of those. So I +don't think yours is the same problem as the original bug report. Which +it's pretty clear involved sshfs. + +As to how .git/info/attributes could be missing: +It is created by `git-annex init`. Upgrading a repository from v5 or older +will also create it. So I don't see how it could normally be missing. At the +moment the most likely reason would be if you had deleted it earlier.. + +(One other way it can be missing is if annex.supportunlocked is set to +false.) +"""]]