diff options
| author |  jesrui@51c25da8d6f34e6df8e3e7ed0277335ed7ddf6a6 <jesrui@web> | 2016-11-10 00:36:05 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-11-10 00:36:05 +0000 |
| commit | fb311c96405bb031a59b858640fd11516e96a2e7 (patch) | |
| tree | 2a3a0a51db9458046cc8391800ef71c9c2d27aa4 | |
| parent | 98f48df6ed0003abee94710b551fa35b1151090d (diff) | |
| -rw-r--r-- | doc/forum/how_to_force_read-only_in_enableremote__63__.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
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 000000000..ff90fbbcd --- /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? |