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

drop unwanted content in the transfer scan

Browse source 
This was complicated quite a bit by needing to check numcopies. I optimised
that, so it only looks up numcopies once per file, no matter how many
remotes it checks to drop from. Although it did just occur to me that
it might be better to first check if it wants to drop content, and only
then check numcopies..
This commit is contained in:
Joey Hess 2012-10-18 14:55:59 -04:00
parent dbe8de40ab
commit f7f34d2072
3 changed files with 57 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/design/assistant/transfer_control.mdwn
View file

@ -30,7 +30,7 @@ the same content, this gets tricky. Let's assume there are not.)
1. The preferred content expression can change, or a new repo is added, or
groups change. Generally, some change to global annex state. Only way to deal
with this is an expensive scan. (The rest of the items below come from
analizing the terminals used in preferred content expressions.)
analizing the terminals used in preferred content expressions.) **done**
2. renaming of a file (ie, moved to `archive/`)
3. some other repository gets the file (`in`, `copies`)
4. some other repository drops the file (`in`, `copies` .. However, it's