From: Junio C Hamano <gitster@pobox.com>
To: Gerrit Pape <pape@smarden.org>
Cc: git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH] git-pull: warn if only fetching tags with the -t switch
Date: Thu, 27 Dec 2007 23:19:00 -0800 [thread overview]
Message-ID: <7vodcbe17f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vve6je349.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 27 Dec 2007 22:37:42 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> It appears that the explicit case also needs documentation.
But with two "oops-correction"s.
> The refs fetched are:
>
> + Having --tags on the command line is the same as replacing
> remote.$remote.fetch with refs/tags/*:refs/tags/* in the
> configuration.
>
> + If refspecs are explicitly given from the command line, they
> will be the ones that are fetched, and remotes.$remote.fetch
> is consulted unless they come from the above --tags.
s/is consulted/is ignored/;
> * Otherwise, remotes.$remote.fetch (and its equivalent in
> .git/remotes/$remote) are the ones that are fetched.
>
> * In addition, if branch.$current_branch.merge is specified but
> is not covered by the above, it also is fetched.
s/if /if no explicit refspecs are given and /;
next prev parent reply other threads:[~2007-12-28 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 12:44 [PATCH] git-pull: don't complain about branch merge config if only fetching tags Gerrit Pape
2007-12-21 16:35 ` Junio C Hamano
2007-12-27 9:30 ` Gerrit Pape
2007-12-27 10:39 ` Junio C Hamano
2007-12-27 14:46 ` [PATCH] git-pull: warn if only fetching tags with the -t switch Gerrit Pape
2007-12-28 6:37 ` Junio C Hamano
2007-12-28 7:19 ` Junio C Hamano [this message]
2007-12-28 17:32 ` Daniel Barkalow
2007-12-28 21:58 ` Junio C Hamano
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=7vodcbe17f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pape@smarden.org \
--cc=spearce@spearce.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).