From 24adb479480327b960d1db2806896f6ed8da8cce Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 10 Jan 2018 13:29:21 -0400 Subject: response --- ...mment_3_b041da6694d9d9d21a67f7bbdda0f62e._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/share_.git__47__annex__47__objects_across_multiple_repositories_on_one_machine/comment_3_b041da6694d9d9d21a67f7bbdda0f62e._comment 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! +"""]] -- cgit v1.2.3