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

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2013-04-16 20:46:09 +00:00 committed by admin
parent 4c1cc14fc1
commit d543df20e3
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/forum/Drop_with_assistant/comment_8_773e540e46adc43487323e8d38ceb2d9._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 8"
date="2013-04-16T20:46:09Z"
content="""
@edheil, you used to be right about the middleman. But I'm continually improving things. :)
So, consider this situation:
> A (client) --- B (client) ---- C (archive)
If a file is created on A, inside an `archive` directory, B wants a copy, since it's not archived yet. Once B gets the copy, it sends it on the C. At that point, B notices that hey, this file was archived and is in an archive directory, and so it no longer wants its copy and drops it.
(At this point A will also want to drop the file. However, it cannot! This is because git-annex requires positive, direct verification that some other repository has a file before dropping it, and A cannot talk to C to check.
However, if you set C to be trusted, this verification is bypassed, and then A will be able to drop the file as well.)
This support for middlemen is a new feature, which will be in the next release. You can get it in any recent nightly build.
Amusingly this feature was built without writing any haskell code.. just fine-tuning the preferred content expressions!
We can also consider what happens if B is set to manual. In this case, it won't automatically get the file from A. But if you manually get it, then B will send it on to C. And A will drop the file once it hears that C has it. Due to the manual mode, you'll have to manually drop it from B of course.
"""]]