From 460992d2a1a9ff76e9ed923be275d17f390ab715 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 1 May 2023 17:08:44 -0400 Subject: [PATCH] comment --- ...comment_6_d107491ed7ac97c4732dc96707defaf0._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Empty_files_make_git_status_slow/comment_6_d107491ed7ac97c4732dc96707defaf0._comment diff --git a/doc/bugs/Empty_files_make_git_status_slow/comment_6_d107491ed7ac97c4732dc96707defaf0._comment b/doc/bugs/Empty_files_make_git_status_slow/comment_6_d107491ed7ac97c4732dc96707defaf0._comment new file mode 100644 index 0000000000..a39d3dc7de --- /dev/null +++ b/doc/bugs/Empty_files_make_git_status_slow/comment_6_d107491ed7ac97c4732dc96707defaf0._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2023-05-01T21:07:19Z" + content=""" +I'm guessing that, in a v10 repo, this is less of a problem, since +git-annex uses git's long-running filter-process interface then. So git can +probably run `git-annex filter-process` once and use it to re-smudge all +the empty files it (for whatever reason) wants to re-smudge. +"""]]