From: Joey Hess Date: Tue, 2 Nov 2021 19:16:15 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~57^2~70 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=be690a071700a7cbfafeb1d6201d65b2db5474b1;p=git-annex.git comment --- diff --git a/doc/bugs/git_commit_smudges_unncessarily/comment_1_202cb8adc7a7b1119f5b4c1f5c6e9c7e._comment b/doc/bugs/git_commit_smudges_unncessarily/comment_1_202cb8adc7a7b1119f5b4c1f5c6e9c7e._comment new file mode 100644 index 0000000000..b31e0002b5 --- /dev/null +++ b/doc/bugs/git_commit_smudges_unncessarily/comment_1_202cb8adc7a7b1119f5b4c1f5c6e9c7e._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-11-02T19:11:51Z" + content=""" +I doubt this bisection was correct. Whether git commit decides to smudge a +file is entirely an internal decision on the part of git; the only way +git-annex can affect it is by updating the mtime etc of the file. + +Even small things like variations in timing can change git's smudging +behavior. It may unncessarily re-smudge a file when its timestamp is +sufficiently close to the current time. For whatever internal value +of "sufficiently close" it happens to pick for a given +OS/filesystem/whatever. +"""]]