diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-12-11 16:22:40 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-12-11 16:22:40 -0400 |
| commit | f9e50ee7922068a2400dc9ddf4b30b059268981b (patch) | |
| tree | 8791d2279b661172fa524ee4fdfeeca40754772e | |
| parent | 04dd602ec1270ad00074ebde80ba35510780a657 (diff) | |
update
| -rw-r--r-- | doc/todo/smudge.mdwn | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index 47613774c..eeb34f135 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -322,8 +322,9 @@ files to be unlocked, while the indirect upgrades don't touch the files. #### implementation todo list * Dropping a smudged file causes git status to show it as modified, - because the timestamp has changed. Avoid this by preserving timestamp - of smudged files when manipulating. + because the timestamp has changed. Getting a smudged file can also + cause this. Avoid this by preserving timestamp of smudged files + when manipulating. * Reconcile staged changes into the associated files database, whenever the database is queried. * See if the cases where the Keys database is not used can be @@ -345,6 +346,7 @@ files to be unlocked, while the indirect upgrades don't touch the files. when pushing changes committed in such a repo. Ideally, should avoid committing implicit unlocks, or should prevent such commits leaking out in pushes. +* Test suite should have a pass that runs with files unlocked. ---- |