mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

todo

Browse source
This commit is contained in:
Joey Hess 2017-09-06 15:46:35 -04:00
commit 3ccf661d7c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 8 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/git-annex-export.mdwn
View file

@ -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

4
doc/todo/export.mdwn
View file

@ -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?