From: Josef Wolf <jw@raven.inka.de>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: error: src refspec refs/heads/master matches more than one.
Date: Fri, 14 Feb 2014 23:53:48 +0100 [thread overview]
Message-ID: <20140214225348.GD17817@raven.inka.de> (raw)
In-Reply-To: <xmqqy51dirjs.fsf@gitster.dls.corp.google.com>
On Fri, Feb 14, 2014 at 08:32:07AM -0800, Junio C Hamano wrote:
> A. You are not allowed to call your branch with a string that begins with
> 'refs/heads/'.
> B. Why?
> A. Because it will confuse you.
> B. I know what I am doing.
> A. ???
Your reply in
http://git.661346.n2.nabble.com/1-8-0-git-checkout-refs-heads-foo-checks-out-branch-foo-td5999936.html
suggests that one should explicitly use the refs/heads prefix to to work
around ambiguities in some situations.
Are there any best-practices sugestions out there about when to use the
refs/heads prefix and when not? It looks like git delibaretly cuts off this
prefix in some situations.
I don't think my problem stems from something like "git branch refs/heads/master"
Anyway, some clarifications about the usage of this prefix would be great!
--
Josef Wolf
jw@raven.inka.de
next prev parent reply other threads:[~2014-02-14 23:00 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140214225348.GD17817@raven.inka.de \
--to=jw@raven.inka.de \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.