summaryrefslogtreecommitdiff
path: root/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment')
-rw-r--r--doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment
new file mode 100644
index 000000000..a949625ad
--- /dev/null
+++ b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-04-09T18:06:34Z"
+ content="""
+I have tried to reproduce this, and I can't seem to.
+
+There's no network traffic involved in git-annex unused --from remote,
+so I don't see how this can involve the S3 backend at all. If there's a bug
+here, it should affect any kind of remote.
+
+Are you sure you didn't forget to `git annex sync` before `git annex unused --from remote`?
+If you have an old synced/master branch, that'll count as a user of the
+file and so unused won't show it.
+
+I think you'll need to provide a full transcript of how to make this problem
+happen for me to get any further.
+"""]]