summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <joey@web>2013-05-23 15:57:08 +0000
committerGravatar admin <admin@branchable.com>2013-05-23 15:57:08 +0000
commitb5493c9601e6f717eed05df3a0178b424a1b4f73 (patch)
tree131d0dedddedb5bc273b04b0b13742cfe7526dfb
parenta1df292455b825dcb8eb47c366735aa615e79259 (diff)
Added a comment
-rw-r--r--doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment
new file mode 100644
index 000000000..859377308
--- /dev/null
+++ b/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 2"
+ date="2013-05-23T15:57:08Z"
+ content="""
+I suppose another way to fix it along similar lines would be to make `git annex copy` always trust location tracking information when deciding whether to copy. I'm not sure how I feel about this though -- it might make things less robust in situations where `git annex copy` is run as a backup, and location tracking could have gotten out of date.
+"""]]