diff options
author | Joey Hess <joeyh@joeyh.name> | 2016-12-02 14:49:22 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2016-12-02 14:54:33 -0400 |
commit | 98838a112219dbf57d5ef3a101122cde180faf9f (patch) | |
tree | 7c985b9bb97da900416240b50f37d0e9847207ce /RemoteDaemon | |
parent | af69d6a45bcb29149eccde2b0d675a551233ff71 (diff) |
initial implementation of P2P.Annex runner
Untested, and it does not yet update transfer logs.
Verifying transferred content is modeled on git-annex-shell recvkey.
In a direct mode or annex.thin repository, content can change while it's
being transferred. So, verification is always done, even if annex.verify
would normally prevent it.
Note that a WORM or URL key could change in a way the verification
doesn't catch. That can happen in git-annex-shell recvkey too. We don't
worry about it, because those key backends don't guarantee preservation
of data. (Which is to say, I worried about it, and then convinced myself
again it was ok.)
Diffstat (limited to 'RemoteDaemon')
0 files changed, 0 insertions, 0 deletions