From: Eric Raible <raible@gmail.com>
To: git@vger.kernel.org
Subject: Re: Question regarding git fetch
Date: Thu, 27 Aug 2009 16:21:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20090827T180201-590@post.gmane.org> (raw)
In-Reply-To: 32541b130908270836m50553ccatddf4c870eec54ddb@mail.gmail.com
Avery Pennarun <apenwarr <at> gmail.com> writes:
> Git currently promises that your refs/remotes/* branches will
> never be updated unless you explicitly request it, even if you're
> fetching, merging, and pulling other stuff.
So your claim is that "git fetch central" is somehow more
explicit than "git fetch central master"?
I understand that "git fetch central" will use
remote.central.fetch (which _is_ explicit), but
the command itself is certainly _less_ explicit about
specifying the remote branch.
Either way, AFAICT it seems purely historical that
"git fetch central master" doesn't update remotes/central.
- Eric
next prev parent reply other threads:[~2009-08-27 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 15:30 Question regarding git fetch Tom Lambda
2009-08-27 15:36 ` Avery Pennarun
2009-08-27 16:21 ` Eric Raible [this message]
2009-08-27 16:28 ` Avery Pennarun
2009-08-27 16:46 ` Björn Steinbrink
2009-08-27 17:22 ` Avery Pennarun
2009-08-27 20:48 ` Jeff King
2009-08-27 21:34 ` Jeff King
2009-08-27 21:44 ` Junio C Hamano
2009-08-27 21:50 ` Jeff King
2009-08-27 21:53 ` Jeff King
2009-08-27 22:12 ` Avery Pennarun
2009-08-27 22:16 ` Jeff King
2009-08-27 22:24 ` Avery Pennarun
2009-08-27 21:20 ` Junio C Hamano
2009-08-27 21:39 ` Jeff King
2009-08-28 13:24 ` Tom Lambda
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20090827T180201-590@post.gmane.org \
--to=raible@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).