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

check preferred content when a file is moved or created

Browse source 
This can result in the file being dropped, or being downloaded, or even
being dropped from some other repo.

It's even possible to create a file in a directory where content is not
wanted, which will make the assistant immediately send it elsewhere, and
then drop it.
This commit is contained in:
Joey Hess 2012-10-19 14:22:13 -04:00
parent 168752ca3b
commit f4c3a45da0
2 changed files with 15 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -33,10 +33,9 @@ the same content, this gets tricky. Let's assume there are not.)
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.) **done**
2. renaming of a file (ie, moved to `archive/`)
(note that renaming a file can also make it become preferred content
again, and should cause it to be transferred in that case, which doesn't
happen either..)
2. renaming of a file (ie, moved to `archive/`) **done**
(note also that renaming a file can also make it become preferred content
again, and should cause it to be transferred in that case) **done**
3. we get a file (`in`, `copies`) **done**
4. we sent a file (`in`, `copies`) **done**
5. some other repository drops the file (`in`, `copies` .. However, it's