diff options
Diffstat (limited to 'doc/todo/export.mdwn')
-rw-r--r-- | doc/todo/export.mdwn | 34 |
1 files changed, 2 insertions, 32 deletions
diff --git a/doc/todo/export.mdwn b/doc/todo/export.mdwn index 3ddca0cf8..6c6789a29 100644 --- a/doc/todo/export.mdwn +++ b/doc/todo/export.mdwn @@ -17,38 +17,8 @@ there need to be a new interface in supported remotes? Work is in progress. Todo list: -* `git annex get --from export` works in the repo that exported to it, - but in another repo, the export db won't be populated, so it won't work. - Maybe just show a useful error message in this case? - - However, exporting from one repository and then trying to update the - export from another repository also doesn't work right, because the - export database is not populated. So, seems that the export database needs - to get populated based on the export log in these cases. - - This needs the db to contain a record of the data source, - the tree that most recently populated it. - - When the export log contains a different tree than the data source, - the export was updated in another repository, and so the - export db needs to be updated. - - Updating the export db could diff the data source with the - logged treeish. Add/delete exported files from the database to get - it to the same state as the remote database. - - When an export is incomplete, the database is in some - state in between the data source tree and the incompletely - exported tree. Diffing won't resolve this. - - When to record the data source? If it's done at the same time the export - is recorded (as no longer incomplete) in the export log, all the files - have not yet been uploaded to the export, and the the database is not - fully updated to match the data source. - - Seems that we need a separate table, to be able to look up filenames - from the export tree by key. That table can be fully populated, - before the Exported table is. +* bug: export db update does not reash disk after Remote.Helper.Export calls + updateExportTree. * tracking exports |