diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-04-08 18:09:05 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-04-08 18:09:05 -0400 |
| commit | cf0126f4366d8b2cc51cfe1319867298d026952a (patch) | |
| tree | 5a8e663cd48ec485f4dc797c1a84f023b7ecdbb8 | |
| parent | 06df1c8607a3de73f350de3480ab070660252fd7 (diff) | |
took another look at this
| -rw-r--r-- | doc/todo/smudge.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index 6103ffa61..b11b1dedc 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -94,11 +94,20 @@ and it slows down *everything*, from `git status` to `git commit`. this. <http://marc.info/?l=git&m=131465033512157&w=2> (Update: apparently can't be fixed.) +> Update: I tried this again (2015) and it seems that git status and git +> add avoid re-sending the file content to the clean filter, as long as the +> file stat has not changed. I'm not sure when git started doing that, +> but it seems to avoid this problem. +> --[[Joey]] + #### smudge The smudge script can also be provided a filename with %f, but it cannot directly write to the file or git gets unhappy. +> Still the case in 2015. Means an unnecesary read and pipe of the file +> even if the content is already locally available on disk. --[[Joey]] + ### dealing with partial content availability The smudge filter cannot be allowed to fail, that leaves the tree and |