diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-08-31 13:29:54 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-08-31 13:33:50 -0400 |
| commit | 36b222bf699023f3e460c8bc231b2916aa27ab5c (patch) | |
| tree | dc538a3362a263f5fee1eedbfe39fa32b88a27d1 /doc | |
| parent | a46a3ce0208f4471368a4070ebd12835375491a5 (diff) | |
resuming exports
Make a pass over the whole exported tree, and upload anything that has
not yet reached the export. Update location log when exporting.
Note that the synthesized keys for non-annexed files are stored in the
location log too.
Some cases involving files in the tree with the same content are not
handled correctly yet.
This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/design/exporting_trees_to_special_remotes.mdwn | 5 | ||||
| -rw-r--r-- | doc/todo/export.mdwn | 10 |
2 files changed, 15 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes.mdwn b/doc/design/exporting_trees_to_special_remotes.mdwn index ce7431141..c9b2b72e5 100644 --- a/doc/design/exporting_trees_to_special_remotes.mdwn +++ b/doc/design/exporting_trees_to_special_remotes.mdwn @@ -175,6 +175,11 @@ except for when the WORM or URL backend is used. So, prevent the user from exporting such keys. Also, force verification on for such special remotes, don't let it be turned off. +The same file contents may be in a treeish multiple times under different +filenames. That complicates using location tracking. One file may have been +exported and the other not, and location tracking says that the content +is present in the export. + ## recording exported filenames in git-annex branch In order to download the content of a key from a file exported diff --git a/doc/todo/export.mdwn b/doc/todo/export.mdwn index f589e953d..354dc84e7 100644 --- a/doc/todo/export.mdwn +++ b/doc/todo/export.mdwn @@ -27,3 +27,13 @@ Work is in progress. Todo list: * 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 + location tracking can be messed up. + + When one of the files is deleted and + that tree is exported, the location log for the key will be updated + to say it's not present, even though the other file is still present. + + 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. |