From: Junio C Hamano <gitster@pobox.com>
To: John Keeping <john@keeping.me.uk>
Cc: Duy Nguyen <pclouds@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Josef Wolf <jw@raven.inka.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: error: src refspec refs/heads/master matches more than one.
Date: Tue, 18 Feb 2014 11:51:05 -0800 [thread overview]
Message-ID: <xmqqtxbwdwt2.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140218193520.GB1048@serenity.lan> (John Keeping's message of "Tue, 18 Feb 2014 19:35:20 +0000")
John Keeping <john@keeping.me.uk> writes:
> There's already the arbitrary set of prefixes in
> refs.c::prettify_refname() and refs.c::ref_rev_parse_rules(). I can see
> how a user might think that since "git log refs/heads/name" is
> equivalent to "git log master" then "git branch refs/heads/name" should
> be equivalent to "git branch name".
Not quite, I am afraid. Branch names used for "git branch <name>"
and "git checkout <name>" are like the Lvalue of an assignment, as
opposed to extended SHA-1 expressions to express any commit
(e.g. 'master^0', 'refs/heads/master', or 'master') that correspond
to the Rvalues used in an expression. Because "git checkout" can
take a branch name or an arbitrary commit object name, there needs a
way for the users to disambiguate.
Saying that "git checkout refs/heads/name" must be equivalent to
"git checkout name" is like arguing that assignment "value+0 = x"
should be valid because "value+0" is a valid value.
For the first parameter to "git branch", there is no ambiguity---it
must be the name of a branch and cannot be an arbitrary commit
object name, so special casing "git branch refs/heads/master" to
mean "git branch master" may not be too bad. But then we need to
either start rejecting "git branch refs/tags/v1.0" or keep allowing
it to create a ref refs/heads/refs/tags/v1.0 to denote the branch of
that exact name given---neither of which is more consistent, so...
next prev parent reply other threads:[~2014-02-18 19:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:31 error: src refspec refs/heads/master matches more than one Josef Wolf
2014-02-14 12:45 ` Andreas Schwab
2014-02-14 12:59 ` Duy Nguyen
2014-02-14 15:16 ` Josef Wolf
2014-02-14 15:35 ` David Kastrup
2014-02-14 16:52 ` Josef Wolf
2014-02-14 16:32 ` Junio C Hamano
2014-02-14 16:52 ` David Kastrup
2014-02-14 19:10 ` Junio C Hamano
2014-02-14 22:53 ` Josef Wolf
2014-02-15 8:53 ` Duy Nguyen
2014-02-17 14:25 ` Ingo Rohloff
2014-02-18 19:03 ` Junio C Hamano
2014-02-18 19:35 ` John Keeping
2014-02-18 19:51 ` Junio C Hamano [this message]
2014-02-18 20:01 ` John Keeping
2014-02-20 4:17 ` Michael Haggerty
2014-02-20 18:22 ` Junio C Hamano
2014-02-18 19:37 ` David Kastrup
2014-02-18 21:47 ` Junio C Hamano
2016-03-23 11:17 ` Duy Nguyen
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=xmqqtxbwdwt2.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=jw@raven.inka.de \
--cc=pclouds@gmail.com \
--cc=schwab@linux-m68k.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).