From: Junio C Hamano <gitster@pobox.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
John Dlugosz <JDlugosz@TradeStation.com>,
git@vger.kernel.org
Subject: Re: fetch and pull
Date: Wed, 18 Mar 2009 02:37:30 -0700 [thread overview]
Message-ID: <7v1vsvi339.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090318085849.GA8118@atjola.homenet> (Björn Steinbrink's message of "Wed, 18 Mar 2009 09:58:49 +0100")
Björn Steinbrink <B.Steinbrink@gmx.de> writes:
> 1) You do "git pull git://host/repo.git" or similar, i.e. you don't use
> a remote. Because then, no refspec is given to fetch, and it defaults to
> fetching HEAD.
> ...
> 1) probably isn't that common for most users, and even if, it's not
> one of the commands given as examples to which the paragraph applies.
I think "a maintainer responds to a pull request" is the only case that
happens often in practice for a fetch+merge of HEAD from a remote
repository.
Even in that case, we strongly encourage people to say not just "which
repository location" but also "which branch", i.e.
Linus, please pull from:
git://git.or.cz/alt-git.git for-linus
to obtain the following commits.
When Linus cuts and pastes that to his shell, the command will become:
$ git pull git://git.or.cz/alt-git.git for-linus
and HEAD is not involved in such a use case.
next prev parent reply other threads:[~2009-03-18 9:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcmmaYOKDtJohyDSQt2B3xvVeIPNPw==>
2009-03-16 19:00 ` fetch and pull John Dlugosz
2009-03-16 20:03 ` Jay Soffian
2009-03-16 20:39 ` John Dlugosz
2009-03-16 20:43 ` Sverre Rabbelier
2009-03-17 8:34 ` Jeff King
2009-03-17 8:36 ` Sverre Rabbelier
2009-03-16 22:14 ` Jay Soffian
2009-03-16 22:33 ` John Dlugosz
2009-03-17 0:09 ` Jay Soffian
2009-03-17 14:58 ` John Dlugosz
2009-03-17 16:21 ` Jay Soffian
2009-03-17 16:44 ` John Dlugosz
2009-03-17 21:31 ` Nanako Shiraishi
2009-03-18 8:58 ` Björn Steinbrink
2009-03-18 9:37 ` Junio C Hamano [this message]
2009-03-18 15:18 ` John Dlugosz
2009-03-18 15:31 ` Björn Steinbrink
2009-03-18 16:50 ` John Dlugosz
2009-03-18 0:37 ` Jeff King
2009-03-06 19:04 John Dlugosz
2009-03-06 19:27 ` Junio C Hamano
2009-03-06 20:44 ` Jakub Narebski
2009-03-06 20:49 ` Junio C Hamano
2009-03-06 22:11 ` John Dlugosz
2009-03-06 22:21 ` Junio C Hamano
2009-03-07 8:00 ` Bryan Donlan
2009-03-07 20:15 ` Junio C Hamano
2009-03-09 15:27 ` John Dlugosz
2009-03-09 15:08 ` John Dlugosz
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=7v1vsvi339.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=B.Steinbrink@gmx.de \
--cc=JDlugosz@TradeStation.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
/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).