response

1 files changed, 20 insertions, 0 deletions

diff --git a/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine/comment_3_b041da6694d9d9d21a67f7bbdda0f62e._comment b/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine/comment_3_b041da6694d9d9d21a67f7bbdda0f62e._comment
new file mode 100644
index 000000000..0a48c1ca6
--- /dev/null
+++ b/doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine/comment_3_b041da6694d9d9d21a67f7bbdda0f62e._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2018-01-10T17:24:04Z"
+ content="""
+@davicastro using --shared makes git-annex not trust the shared clone, 
+which is necessary to avoid situations that could result in data loss.
+The downside though, is that the lack of trust can change git-annex
+behavior in some situations.
+
+For example, normally you can run `git annex get myfile` and then `git
+annex drop myfile --from someremote` will remove it from the remote, since
+you now have a local copy. But, with the shared clone being untrusted, the
+drop will fail if it would be the only remaining copy of the file. In
+this situation, you would need to first `git annex copy myfile --to origin`
+or something like that before dropping.
+
+Of course, that copy would run fast and cheap since it only has to make a
+hardlink!
+"""]]