From 4cc698549423e0619294254e90f6c4f4a045db27 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 22 Nov 2019 19:47:53 -0400 Subject: [PATCH] todo --- .../git_status_smudges_unncessarily_after_unlock.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/git_status_smudges_unncessarily_after_unlock.mdwn diff --git a/doc/todo/git_status_smudges_unncessarily_after_unlock.mdwn b/doc/todo/git_status_smudges_unncessarily_after_unlock.mdwn new file mode 100644 index 0000000000..b1b59f0869 --- /dev/null +++ b/doc/todo/git_status_smudges_unncessarily_after_unlock.mdwn @@ -0,0 +1,11 @@ +After unlocking a file, `git status` runs the smudge filter. That is +unnecessary, and when many files were unlocked, it can take a long time +because [[git_smudge_clean_interface_suboptiomal]] means it runs git-annex +once per file. + +It should be possible to avoid that, as was done with git drop in [[!commit +1113caa53efedbe7ab1d98b74010160f20473e8d]]. I tried making Command.Unlock +use restagePointerFile, but that did not help; git update-index does then +smudge it during the `git annex unlock`, which is no faster (but at least +doing it then would avoid the surprise of a slow `git status` or `git +commit -a`). Afterwards, `git status` then smudged it again, unsure why!