From: Kevin Daudt Date: Tue, 03 Mar 2015 23:11:59 GMT Subject: [PATCH 1/2] docs: explain behaviour with no tagopt set Message-ID: <1425424320-4091-1-git-send-email-me@ikke.info> Currently, only the behaviour when this option is set is explained, but it's unclear what happens when this option hasn't been set. Signed-off-by: Kevin Daudt --- Documentation/config.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 440784c..394042a 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -2241,8 +2241,9 @@ remote..tagopt:: Setting this value to \--no-tags disables automatic tag following when fetching from remote . Setting it to \--tags will fetch every tag from remote , even if they are not reachable from remote - branch heads. Passing these flags directly to linkgit:git-fetch[1] can - override this setting. See options \--tags and \--no-tags of + branch heads. When not set, fetches only tags reachable by the + downloaded refs. Passing these flags directly to linkgit:git-fetch[1] + can override this setting. See options \--tags and \--no-tags of linkgit:git-fetch[1]. remote..vcs:: -- 2.3.0