From ba0de2d26a6eca77bebef1931d2b41bf04a93303 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 2 Feb 2021 12:33:01 -0400 Subject: [PATCH] comment --- ..._1df979b8e222dd135a10046c51f0dc0b._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_6_1df979b8e222dd135a10046c51f0dc0b._comment diff --git a/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_6_1df979b8e222dd135a10046c51f0dc0b._comment b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_6_1df979b8e222dd135a10046c51f0dc0b._comment new file mode 100644 index 0000000000..d055b0dae7 --- /dev/null +++ b/doc/bugs/after_adjust_--unlock_implies__44___a_lot_of_files_are_reported_as_modified/comment_6_1df979b8e222dd135a10046c51f0dc0b._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2021-02-02T16:28:29Z" + content=""" +Being on sshfs makes me wonder if perhaps something synthesized by that +filesystem is confusing git, so eg it thinks the inode or mtime of a file has +changed and so it's modified. + +However, normally git status does the same work to verify if there's really +a modification as git diff does (running the smudge filter in this case). +So I'm not clear what's going on here, but it's currently looking more like +a problem at the git level, or a filesystem that is too wonky for git to +work well, rather than anything git-annex can do. + +I have to wonder why you'd even use git-annex on sshfs. The more usual way +would be to have a local repository with a remote using ssh to access the +server. +"""]] -- 2.30.2