From b5eacd6be31db5451c39929b69533956971ec386 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 16 Jun 2021 12:07:08 -0400 Subject: [PATCH] comment --- ...3_6c7c92a9c5ce9cee1450117f0bab1354._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/tips/disabling_a_special_remote/comment_3_6c7c92a9c5ce9cee1450117f0bab1354._comment diff --git a/doc/tips/disabling_a_special_remote/comment_3_6c7c92a9c5ce9cee1450117f0bab1354._comment b/doc/tips/disabling_a_special_remote/comment_3_6c7c92a9c5ce9cee1450117f0bab1354._comment new file mode 100644 index 0000000000..869455a017 --- /dev/null +++ b/doc/tips/disabling_a_special_remote/comment_3_6c7c92a9c5ce9cee1450117f0bab1354._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-06-16T16:02:04Z" + content=""" +This tip is mostly talking about the web special remote, which is unusual +in that it's enabled by default. So there is nothing in `.git/config` about +it. + +Any special remote that you set up with `initremote` or `enableremote` does +have a section in `.git/config` same as a regular git remote would +(just with git-annex specific configs in there). So `git remote` +can be used to list it, and `git remote rm` will disable it. + +As far as setting annex-ignore goes, it prevents git-annex from using that +remote *unless* you explicitly ask it to. @yarikoptic's example above +sets that for a remote and then explicitly fscks it. +"""]]