From: David Kastrup <dak@gnu.org>
To: Josef Wolf <jw@raven.inka.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: error: src refspec refs/heads/master matches more than one.
Date: Fri, 14 Feb 2014 16:35:14 +0100 [thread overview]
Message-ID: <87ppmp3dxp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20140214151619.GB17817@raven.inka.de> (Josef Wolf's message of "Fri, 14 Feb 2014 16:16:19 +0100")
Josef Wolf <jw@raven.inka.de> writes:
> On Fri, Feb 14, 2014 at 07:59:18PM +0700, Duy Nguyen wrote:
>> On Fri, Feb 14, 2014 at 7:45 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> > Josef Wolf <jw@raven.inka.de> writes:
>> >
>> >> Notice the refs/heads _within_ refs/heads!
>> > Probably you did something like "git branch refs/heads/master". You can
>> > remove it again with "git branch -d refs/heads/master".
>> As a porcelain, "git branch" should prevent (or at least warn) users
>> from creating such refs, I think.
>
> I don't think I did it the way Andreas thinks. This repository is maintained
> by a script, I don't create branches manually. The only command in this script
> that uses "heads" is
>
> git symbolic-ref HEAD "refs/heads/$new_branch"
>
> to create new branches without any ancestry. And I double-checked that this
> command is _not_ resposible for those ghost branches.
>
> BTW: I see such ghost branches reappearing again and again, so it must be
> something systematic.
You probably should check how $new_branch comes about. Also, once a
directory refs/heads/refs/heads exists, "refs/heads/$new_branch" may
possibly be resolved as a branch with the name refs/heads/$new_branch.
--
David Kastrup
next prev parent reply other threads:[~2014-02-14 15:35 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 [this message]
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
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=87ppmp3dxp.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/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).