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/git-annex-export.mdwn | |
| parent | 6fcefbdb6629c3e94c41bc05a6b7c224ade99ba0 (diff) | |
todo
Diffstat (limited to 'doc/git-annex-export.mdwn')
| -rw-r--r-- | doc/git-annex-export.mdwn | 7 |
1 files changed, 4 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 |