Subject: Re: [PATCH] git-remote.txt: describe behavior without --tags and --no-tags

From: Francis Moreau <[email-masked]>
Date: Mon, 02 Mar 2015 15:56:17 +0100

On 03/02/2015 03:48 PM, Michael J Gruber wrote:
> Francis Moreau venit, vidit, dixit 02.03.2015 14:36:
>> Hi,
>>
>> On 03/02/2015 02:08 PM, Michael J Gruber wrote:
>>> Signed-off-by: Michael J Gruber <[email-masked]>
>>> ---
>>>  Documentation/git-remote.txt | 5 ++++-
>>>  1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
>>> index a77607b..f3f6f0d 100644
>>> --- a/Documentation/git-remote.txt
>>> +++ b/Documentation/git-remote.txt
>>> @@ -56,7 +56,10 @@ With `--tags` option, `git fetch <name>` imports every tag from the
>>>  remote repository.
>>>  +
>>>  With `--no-tags` option, `git fetch <name>` does not import tags from
>>>  the remote repository.
>>> ++
>>> +By default, only tags on fetched branches are imported
>>> +(see linkgit:git-fetch[1]).
>>>  +
>>
>> So the default is neither --no-tags nor --tags ?
>>
>> Thanks.
>>
> 
> By default, only tags on fetched branches are imported. That is: When
> the fetch is done, all tags are imported that point to commits that are
> reachable from refs that you are fetching, in short: "tags on fetched
> branches". That is in between "none" (--no-tags) and "all" (--tags).
> 

just my 2 cents, I would find easier to read it like this:

-----
By default, only tags on fetched branches are imported. This can be
changed by the --tags and --no-tags options.

With `--tags` option, `git fetch <name>` imports every tag from the
remote repository (including not reachable tags from fetched refs).

With `--no-tags` option, `git fetch <name>` does not import tags from
the remote repository.
-----

Thanks.