| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | added StoreContentTo |  Joey Hess | 2016-12-06 |
| | | | | | | | | | This is needed in addition to StoreContent, because retrieveKeyFile can be used to retrieve to different destination files, not only the tmp file for a key. This commit was sponsored by Ole-Morten Duesund on Patreon. | ||
| * | plumb assicated files through P2P protocol for updating transfer logs | Joey Hess | 2016-12-02 |
| | | | | | | | | | | | ReadContent can't update the log, since it reads lazily. This part of the P2P monad will need to be rethought. Associated files are heavily sanitized when received from a peer; they could be an exploit vector. This commit was sponsored by Jochen Bartl on Patreon. | ||
| * | plumb peer uuid through to runLocal | Joey Hess | 2016-12-02 |
| | | | | | This will allow updating transfer logs with the uuid. | ||
| * | initial implementation of P2P.Annex runner | Joey Hess | 2016-12-02 |
| | | | | | | | | | | | | | | | | 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.) | ||
| * | improve Local monad | Joey Hess | 2016-12-02 |
| | | |||
| * | cleanups | Joey Hess | 2016-12-01 |
| | | |||
| * | reorg | Joey Hess | 2016-11-22 |
 |
index : git-annex-gpl | |
| git-annex without the AGPL |
| summaryrefslogtreecommitdiff |