71ddb10699
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.) |
||
|---|---|---|
| .. | ||
| Address.hs | ||
| Annex.hs | ||
| Auth.hs | ||
| IO.hs | ||
| Protocol.hs | ||