From: Joey Hess Date: Tue, 25 Jan 2022 16:38:02 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~53^2~315 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=a5854f181ddf54cd46917cb876307fe3a8599e4d;p=git-annex.git comment --- diff --git a/doc/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_2_cefd5742da29e19f5ab3406698a13f9f._comment b/doc/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_2_cefd5742da29e19f5ab3406698a13f9f._comment new file mode 100644 index 0000000000..1f18a3cd72 --- /dev/null +++ b/doc/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_2_cefd5742da29e19f5ab3406698a13f9f._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-01-25T16:36:20Z" + content=""" +git can sometimes get into a situation where it is unsure about the status +of working tree files, and when those files are not git-annex symlinks but +either unlocked git-annex files or regular files checked into git, it needs +to run `git-annex smudge` once per file. That can take a long time when it +somehow needs to check many files. + +This kind of slowdown is largely avoided by setting: + + git config filter.annex.process 'git-annex filter-process' + +Which will be handled automatically by a future upgrade. +"""]]