summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-12-11 15:31:34 +0000
committerGravatar admin <admin@branchable.com>2013-12-11 15:31:34 +0000
commit0ec33f100f4080d87b946981fa6be5ea2e5574f8 (patch)
treef16dd766354cf9c285002e881c1b15129a565532 /doc
parent2985bcad99b0bf31ef76c3aae33a3857519870b3 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/--quite_with_s3/comment_1_5f51452d939d61496e97805310746ea3._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/--quite_with_s3/comment_1_5f51452d939d61496e97805310746ea3._comment b/doc/bugs/--quite_with_s3/comment_1_5f51452d939d61496e97805310746ea3._comment
new file mode 100644
index 000000000..07cb1b780
--- /dev/null
+++ b/doc/bugs/--quite_with_s3/comment_1_5f51452d939d61496e97805310746ea3._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.87"
+ subject="comment 1"
+ date="2013-12-11T15:31:34Z"
+ content="""
+So, `git annex copy --to remote` currently does an active check that the remote has each file. This is a bit inneficient, and I have never been 100% sure that's the best thing, but from time to time I see a situation where trusting the location log when doing a `cp` would not be ideal.
+
+It would be easy to omit the output for files that the check finds on the remote, but I think it's good because it tells you git-annex is doing actual work. Otherwise, `git annex copy --to remote` might seem to take a long time for no reason.
+
+Anyway, you can disable the active check, with --fast. And I agree that in this case it would be better to not print anything. I looked at the code and it would be a little tricky to do it.
+
+There's a simple workaround: `git annex copy --to remote --not --in remote`
+"""]]