summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-12-09 15:42:16 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-12-09 15:52:11 -0400
commitb5c8ba7db3ea2eb4f1cd28e49cadb5fd348ca738 (patch)
tree81d2f8bca341e56bb20d01d68e0a60812e285aa2 /doc
parent7f00b7eaf0877e791194e7dfed5abefbb091ee86 (diff)
move InodeSentinal from direct mode code to its own module
Will be used outside of direct mode for v6 unlocked files, and is already used outside of direct mode when adding files to annex.
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/smudge.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn
index 373c65561..60cc65f3f 100644
--- a/doc/todo/smudge.mdwn
+++ b/doc/todo/smudge.mdwn
@@ -325,12 +325,12 @@ files to be unlocked, while the indirect upgrades don't touch the files.
#### implementation todo list
-* inAnnex check should fail in the case where an annexed objects is unlocked
+* inAnnex check should fail in the case where an annexed object is unlocked
and has had its content changed. Could use an InodeCache for
such objects. This parallels how inAnnex checks work for direct mode.
* Reconcile staged changes into the associated files database, whenever
the database is queried.
-* See if the case where the associated files database is not used can be
+* See if the cases where the associated files database is not used can be
optimised. Eg, if the associated files database doesn't exist at all,
we know smudge/clean are not used, so queries for associated files don't
need to open the database or do reconciliation, but can simply return none.