From 87507722cb9a45ca2fd6168f2af3e41ea3ab7b1a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 6 Jul 2018 12:38:41 -0400 Subject: [PATCH] comment --- ...nt_3_790ce76fe02ca35b9da7309ee2384c01._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/todo/append-only_mode/comment_3_790ce76fe02ca35b9da7309ee2384c01._comment diff --git a/doc/todo/append-only_mode/comment_3_790ce76fe02ca35b9da7309ee2384c01._comment b/doc/todo/append-only_mode/comment_3_790ce76fe02ca35b9da7309ee2384c01._comment new file mode 100644 index 0000000000..d4eac48cf2 --- /dev/null +++ b/doc/todo/append-only_mode/comment_3_790ce76fe02ca35b9da7309ee2384c01._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2018-07-06T16:34:02Z" + content=""" +I think it would go better in a tips page than on the man page. +Especially since no complete solution is available and it's well beyond the +scope of a manpage for git-annex-shell to document such a solution. + +It seems to me that allowing untrusted people to push to the git-annex +branch is asking for various mischeif. One that comes to mind is they can +add a repository, configure it to be trusted, and make git-annex think +it has a copy of all content. Combined with preferred content settings this +could make git-annex drop the only actual copy of content. +"""]]