diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-12-10 14:29:34 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-12-10 14:50:52 -0400 |
| commit | dd4d3a4c327948a24bf0e2c7cf82ed66999437aa (patch) | |
| tree | ff6740b01aecc0c66f8f79a156c06ae3ed5a6e4c /doc | |
| parent | 1dd612b2b106911433b0d3f6593ba7c2ce48483a (diff) | |
check inode cache in prepSendAnnex
This does mean one query of the database every time an object is sent.
May impact performance.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/smudge.mdwn | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index cc8da67d0..c203c9566 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -328,8 +328,6 @@ files to be unlocked, while the indirect upgrades don't touch the files. * 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. -* Also, Annex.Content.prepSendAnnex should check the InodeCache for - changes. * Reconcile staged changes into the associated files database, whenever the database is queried. * See if the cases where the associated files database is not used can be |