From d7f386a81d5784de3d5e0f3ac07cdebaee6ceea0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Aug 2018 12:20:58 -0400 Subject: [PATCH] reproduced with current --- ..._d3a05649e8d7d5d62cc3e80ce0f45fe4._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/Empty_files_make_git_status_slow/comment_4_d3a05649e8d7d5d62cc3e80ce0f45fe4._comment diff --git a/doc/bugs/Empty_files_make_git_status_slow/comment_4_d3a05649e8d7d5d62cc3e80ce0f45fe4._comment b/doc/bugs/Empty_files_make_git_status_slow/comment_4_d3a05649e8d7d5d62cc3e80ce0f45fe4._comment new file mode 100644 index 0000000000..9c43129ea6 --- /dev/null +++ b/doc/bugs/Empty_files_make_git_status_slow/comment_4_d3a05649e8d7d5d62cc3e80ce0f45fe4._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2018-08-27T16:17:32Z" + content=""" +Verified to still be the case with current git-annex +and git 2.18.0. + +I suppose one workaround would be to default annex.largefiles to your +setting. + +But, the user might want to use `git annex export`, which currently exports +only annexed file, not in-git files. Or there might be a workflow with +git-annex metadata, which likewise can only be added to annexed files. Such +a special case by default may be more trouble than it's worth. + +I'm guessing that git uses 0 size in the index to indicate it doesn't know +the stat information for the file, or something like that. Perhaps git +could be changed to use 0 inode instead. +"""]]