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

Added a comment: does it really need to be a new command ("export") or could be the same old "copy"?

Browse source
This commit is contained in:
yarikoptic 2017-07-11 22:14:39 +00:00 committed by admin
parent 37a6bef639
commit 215e1420f2
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="does it really need to be a new command ("export") or could be the same old "copy"?"
date="2017-07-11T22:14:39Z"
content="""
or it could be just a mode of operation for a special remote depending on \"exporttree=true\" being set, where in one (old) case it would operate based on keys associated with the files pointed on the cmdline (or just keys for --auto or pointed by metadata), whenever when \"exporttree=true\" -- it would operate on filenames pointed on command line (or files found to be associated with the keys as pointed by --auto or by metadata)?
Then the same 'copy --to' could be used in both cases, streamlining user experience ;)
"""]]