diff options
| author |  yarikoptic <yarikoptic@web> | 2017-07-11 22:14:39 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-07-11 22:14:39 +0000 |
| commit | e68118be64df2b5d43708d9edd2ab18b2cc6e255 (patch) | |
| tree | 0f6bf7e36ed86b1f1e4531f74078b196230a97bd /doc/design | |
| parent | 3a7e8f6fb026c4328c959e4bc6e6dca2a7fa78bf (diff) | |
Added a comment: does it really need to be a new command ("export") or could be the same old "copy"?
Diffstat (limited to 'doc/design')
| -rw-r--r-- | doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment b/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment new file mode 100644 index 000000000..377d167f7 --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment @@ -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 ;) +"""]] |