From 9dc4f67f49f29561ed809a4e03ee8ed575f29138 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" Date: Sun, 27 Apr 2014 15:04:09 +0000 Subject: [PATCH] Added a comment --- .../comment_1_11af589cf646cb7552eeb5c7401934f5._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment new file mode 100644 index 0000000000..a8a4af4cf1 --- /dev/null +++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" + nickname="Matt" + subject="comment 1" + date="2014-04-27T15:04:09Z" + content=""" +Thinking about it some more perhaps it's not a reasonable thing to do if you don't want people to be able to discover info about the repo. However it would be good to somehow prevent git-annex from running a local init operation when working with a gcrypt repo. +"""]]