From ed742953f2f433ef5e8f02f734789d2684aaaf87 Mon Sep 17 00:00:00 2001 From: "jesrui@51c25da8d6f34e6df8e3e7ed0277335ed7ddf6a6" Date: Thu, 10 Nov 2016 00:36:05 +0000 Subject: [PATCH] --- doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn diff --git a/doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn b/doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn new file mode 100644 index 0000000000..ff90fbbcdc --- /dev/null +++ b/doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn @@ -0,0 +1,3 @@ +I see that `enableremote` changes the source remote to log the presence of a new annex (the annex where `enableremote` was called). I have tested with a gcrypt remote and I see that a new commit appears in the git-annex branch of the source remote after `enableremote` was called. Since I have cloned the annex just for testing and will delete it afterwards, I would like to leave the original remote untouched. + +Is there a way to enable the remote read-only?