response

1 files changed, 19 insertions, 0 deletions

diff --git a/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment b/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment
new file mode 100644
index 000000000..e38def8ba
--- /dev/null
+++ b/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 19"""
+ date="2015-10-12T17:10:21Z"
+ content="""
+@darkfeline I suppose you're talking about two completely disjoint git
+repositories, and not two clones of the same parent repo.
+
+If you don't use fileprefix, and have the same file in two disjoint
+repositories, git-annex will pick the same key for it in both cases, and
+so you'll get deduplication, but only if you don't use different
+fileprefixes.
+
+And this will mostly work pretty well. The danger is, if you drop the file
+from the S3 repo, because say, it's not used anymore in one repository,
+then you're also removing it from the S3 repo as used by the other
+repository. If that was the last copy of the file, that may not be what you
+want.
+"""]]