bugs/git commit smudges unncessarilygit-annexhttp://git-annex.branchable.com/bugs/git_commit_smudges_unncessarily/git-annexikiwiki2022-09-24T19:43:47Zcomment 1http://git-annex.branchable.com/bugs/git_commit_smudges_unncessarily/comment_1_202cb8adc7a7b1119f5b4c1f5c6e9c7e/joey2021-11-02T19:24:34Z2021-11-02T19:11:51Z
<p>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.</p>
<p>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.</p>
comment 2http://git-annex.branchable.com/bugs/git_commit_smudges_unncessarily/comment_2_5b230c4b74da48099e8be0e264bbf3e6/joey2021-11-09T20:05:08Z2021-11-09T20:03:33Z
<p>While I still need to investigate if there is really a reversion here,
it's worth noting that you can probably avoid the slow speed by running:</p>
<p>git config filter.annex.process 'git-annex filter-process'</p>
<p>That needs a current daily build of git-annex, the feature will also be in
the next release.</p>
comment 3http://git-annex.branchable.com/bugs/git_commit_smudges_unncessarily/comment_3_c30e84ae438810cbab70c401fd5125c0/asakurareiko2022-09-24T19:43:47Z2022-09-24T19:43:47Z
This seems to be fixed now, maybe due to the changes made related to <a href="http://git-annex.branchable.com/todo/git_status_smudges_unncessarily_after_unlock/">git status smudges unncessarily after unlock</a>.