mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

check inode cache in prepSendAnnex

Browse source 
This does mean one query of the database every time an object is sent.
May impact performance.
This commit is contained in:
Joey Hess 2015-12-10 14:29:34 -04:00
parent 3b2a7f216d
commit 2b8f6b8b2f
Failed to extract signature
3 changed files with 21 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/todo/smudge.mdwn
View file

@ -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