response

diff --git a/doc/forum/Multiple_interface_to_the_same_annex/comment_1_ea9e3a987112d8bf6421be234bf61d3c._comment b/doc/forum/Multiple_interface_to_the_same_annex/comment_1_ea9e3a987112d8bf6421be234bf61d3c._comment
new file mode 100644 (file)
index 0000000..df21114
--- /dev/null
+++ b/doc/forum/Multiple_interface_to_the_same_annex/comment_1_ea9e3a987112d8bf6421be234bf61d3c._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-12-13T16:55:21Z"
+ content="""
+Creating a separate special remote pointing to the same content is not a
+good idea. This will confuse git-annex's location tracking, and in some
+cases can lead to data loss, since git-annex will assume it can safely
+delete a file from one of the "two" repositories, since it thinks the
+"other" one will still have the content of the file.
+
+Instead, you need a way to configure a regular git remote,
+pointing at the repository, that is read-only, or is accessed over rsync,
+or whatever your requirements are. 
+"""]]