diff options
author | 2016-12-13 12:58:22 -0400 | |
---|---|---|
committer | 2016-12-13 12:58:22 -0400 | |
commit | a06e7094dcc7c9d3dfeea069f56d6b90e8aa0c18 (patch) | |
tree | 0eaca5d66070fdf70437d620fa4a4c0c28b7f187 /doc | |
parent | 7e89ba2226326fddcfe2355435e7b80bff8fa3ba (diff) |
response
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/Multiple_interface_to_the_same_annex/comment_1_ea9e3a987112d8bf6421be234bf61d3c._comment | 15 |
1 files changed, 15 insertions, 0 deletions
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 index 000000000..df21114bc --- /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. +"""]] |