diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-09-06 15:46:35 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-09-06 15:46:35 -0400 |
commit | 87ac73c70d33e15a537205d2d942bdfc4903dae7 (patch) | |
tree | b4518be7867e0c0215fa389229e9e0890a7cce3c /doc | |
parent | 6fcefbdb6629c3e94c41bc05a6b7c224ade99ba0 (diff) |
todo
Diffstat (limited to 'doc')
-rw-r--r-- | doc/git-annex-export.mdwn | 7 | ||||
-rw-r--r-- | doc/todo/export.mdwn | 4 |
2 files changed, 8 insertions, 3 deletions
diff --git a/doc/git-annex-export.mdwn b/doc/git-annex-export.mdwn index e3cbcbd7a..72319a8fc 100644 --- a/doc/git-annex-export.mdwn +++ b/doc/git-annex-export.mdwn @@ -15,8 +15,9 @@ keys. That is great for reliable data storage, but your filenames are obscured. Exporting replicates the tree to the special remote as-is. Mixing key/value storage and exports in the same remote would be a mess and -so is not allowed. You have to configure a remote with `exporttree=yes` -when initially setting it up with [[git-annex-initremote]](1). +so is not allowed. You have to configure a special remote with +`exporttree=yes` when initially setting it up with +[[git-annex-initremote]](1). Repeated exports are done efficiently, by diffing the old and new tree, and transferring only the changed files. @@ -54,7 +55,7 @@ export`, it will detect the export conflict, and resolve it. [[git-annex]](1) -[[git-annex-export]](1) +[[git-annex-initremote]](1) # AUTHOR diff --git a/doc/todo/export.mdwn b/doc/todo/export.mdwn index f345534e8..24b49ca85 100644 --- a/doc/todo/export.mdwn +++ b/doc/todo/export.mdwn @@ -17,6 +17,10 @@ there need to be a new interface in supported remotes? Work is in progress. Todo list: +* initremote: Don't allow "exporttree=yes" to be set when the special remote + does not support exports. That would be confusing since the user would + set up a special remote for exports, but `git annex export` to it would + later fail.. * `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? |