diff options
| author |  marek@33e8ba4fbc201af14a2badcc0656024401f5c916 <marek@web> | 2016-12-04 15:28:41 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-12-04 15:28:41 +0000 |
| commit | dcc6ade76ec42196b6a37e8b05170bc51187803b (patch) | |
| tree | 219b80c658b9f13f0150375e905a945a4580e6ed /doc | |
| parent | 84361b45d676d8112e822ef7d2183f8028de9d9e (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/more_intelligent_copy_.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/more_intelligent_copy_.mdwn b/doc/forum/more_intelligent_copy_.mdwn new file mode 100644 index 000000000..1c9889a74 --- /dev/null +++ b/doc/forum/more_intelligent_copy_.mdwn @@ -0,0 +1,15 @@ +Hi, + +I noticed, that + +git annex copy --to REMOTE FILES + +and + +git annex copy --to REMOTE --not --in REMOTE FILES + +behave differently. The first does not check, whether file contents are already in the remote the latter does that. I realize that this mimics "normal" (UNIX) copy behaviour but I was not entirely certain this was desired. +Depending on the type of the remote and its configuration (encryption) the latter is considerably faster. + +Just my two cents. + |