From: Junio C Hamano <gitster@pobox•com>
To: Lewis Diamond <git@lewisdiamond•com>
Cc: git@vger•kernel.org
Subject: Re: The fetch command should "always" honor remote.<name>.fetch
Date: Mon, 07 Apr 2014 11:23:21 -0700 [thread overview]
Message-ID: <xmqqioqlm21y.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5340871D.8070503@lewisdiamond.com> (Lewis Diamond's message of "Sat, 05 Apr 2014 18:43:41 -0400")
Lewis Diamond <git@lewisdiamond•com> writes:
> 'git fetch foo develop' would result in:
> fatal: Couldn't find remote ref test2 //Not OK, (case 1)
I have no idea where the "test2" comes from, as it does not appear
anywhere in the above write-up, and it could be a bug.
> 'git fetch foo master' would result in (FETCH_HEAD omitted):
> [new ref] refs/heads/master -> foo/master //OK, but missing another
> ref! (case 2)
> //It should also fetch refs/users/bob/heads/master -> foo/bob/master
This is an incorrect expectation.
The user who gave the command line said only "master", and did not
want to grab "users/bob/heads/master". If the user wanted to get it
as well, the command line would have said so, e.g.
git fetch there master users/bob/heads/master
> If you remove this configuration line: fetch =
> +refs/heads/*:refs/remotes/foo/*
> Then you run 'git fetch foo master', this would result in:
> * branch master -> FETCH_HEAD //Debatable whether this is OK or not,
> but it's definitely missing bob's master! (case 3)
Likewise.
The 'master' short-hand is designed not to match refs/users/any/thing.
next prev parent reply other threads:[~2014-04-07 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 22:43 The fetch command should "always" honor remote.<name>.fetch Lewis Diamond
2014-04-07 18:23 ` Junio C Hamano [this message]
2014-04-07 18:46 ` Lewis Diamond
2014-04-09 1:45 ` Junio C Hamano
2014-04-09 15:57 ` Lewis Diamond
2014-04-09 18:40 ` 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=xmqqioqlm21y.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@lewisdiamond$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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