implement export.log and resolve export conflicts

Incremental export updates work now too.

This commit was sponsored by Anthony DeRobertis on Patreon.
This commit is contained in:
Joey Hess 2017-08-31 15:41:48 -04:00
parent bb08b1abd2
commit 978885247e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
6 changed files with 126 additions and 40 deletions

View file

@ -17,14 +17,10 @@ there need to be a new interface in supported remotes?
Work is in progress. Todo list:
* Remember the previously exported tree (in git-annex branch, see design)
and use to make next export more efficient.
* Only export to remotes that were initialized to support it.
* Prevent using export remotes for key/value storage.
* When exporting, update location tracking to allow getting from exports,
* Use retrieveExport when getting from export remotes.
* Efficient handling of renames.
* Detect export conflicts (see design)
* Support export to aditional special remotes (S3 etc)
* Support export to external special remotes.
* If the same content is present in two different files, export
@ -36,4 +32,4 @@ Work is in progress. Todo list:
And, once one of the files is uploaded, the location log will
say the content is present, so the pass over the tree won't try to
upload the other file.
upload the other file. (See design for a fix for this.)