From 2c014e97dd3bb0e0193b326bf34d4cc25c82bbfc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 19 Dec 2015 14:27:22 -0400 Subject: [PATCH] comment --- ...nt_7_ceb1d2a0e5bbc73590b80ff69292102d._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/devblog/day_339_smudging_out_direct_mode/comment_7_ceb1d2a0e5bbc73590b80ff69292102d._comment diff --git a/doc/devblog/day_339_smudging_out_direct_mode/comment_7_ceb1d2a0e5bbc73590b80ff69292102d._comment b/doc/devblog/day_339_smudging_out_direct_mode/comment_7_ceb1d2a0e5bbc73590b80ff69292102d._comment new file mode 100644 index 0000000000..7de202eac0 --- /dev/null +++ b/doc/devblog/day_339_smudging_out_direct_mode/comment_7_ceb1d2a0e5bbc73590b80ff69292102d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2015-12-19T18:21:04Z" + content=""" +I'm still not entirely happy with the smudge/clean interface's performance. +At least git doesn't fall over if the clean filter declines to read all the +content of the large file on stdin anymore, which was the main thing +preventing an optimised use of it. Still, git has to run the clean filter once +per file, which is suboptimal. And, the smudge filter can't modify the file in +the work tree, but instead has to pass the whole file content back to git +for writing, which is going to result in a lot of unnecessary context +switches and slowdown. Especially in git-annex's case, where all it really +needs to do is make a hard link to the content. +"""]]