From cc2d78870cd6e9d55b6e2ec46abfb30a8fd4debb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 11 Dec 2015 16:22:40 -0400 Subject: [PATCH] update --- doc/todo/smudge.mdwn | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index 47613774ca..eeb34f1350 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. ----