From: Michael J Gruber <git@drmicha.warpmail.net>
To: Francis Moreau <francis.moro@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-remote.txt: describe behavior without --tags and --no-tags
Date: Mon, 02 Mar 2015 15:48:33 +0100 [thread overview]
Message-ID: <54F47841.6060009@drmicha.warpmail.net> (raw)
In-Reply-To: <54F46758.4070207@gmail.com>
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 <git@drmicha.warpmail.net>
>> ---
>> 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).
Michael
next prev parent reply other threads:[~2015-03-02 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 9:48 git-remote add: --no-tags/--tags which one is the default option Francis Moreau
2015-03-02 13:08 ` [PATCH] git-remote.txt: describe behavior without --tags and --no-tags Michael J Gruber
2015-03-02 13:36 ` Francis Moreau
2015-03-02 14:48 ` Michael J Gruber [this message]
2015-03-02 14:56 ` Francis Moreau
2015-03-03 22:09 ` git-remote add: --no-tags/--tags which one is the default option Kevin Daudt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F47841.6060009@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).