git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: error: src refspec refs/heads/master matches more than one.

From
JWJosef Wolf <jw@raven.inka.de>
Date
Feb 14, 2014, 15:16 UTC
Message-ID
<20140214151619.GB17817@raven.inka.de>
In-Reply-To
<CACsJy8BevKQaRLYMMv7bTjf_ZAOnkrimws519OyhGZz6_Vr_-A@mail.gmail.com>
On Fri, Feb 14, 2014 at 07:59:18PM +0700, Duy Nguyen wrote:
Show 8 quoted lines
> 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.
-- 
Josef Wolf
jw@raven.inka.de
Previous: Duy NguyenNext: David Kastrup
Message 4 of 21 in “error: src refspec refs/heads/master matches more than one.”
  1. Josef WolfFeb 14, 2014
  2. Andreas SchwabFeb 14, 2014
  3. Duy NguyenFeb 14, 2014
  4. Josef WolfFeb 14, 2014
  5. David KastrupFeb 14, 2014
  6. Josef WolfFeb 14, 2014
  7. Junio C HamanoFeb 14, 2014
  8. David KastrupFeb 14, 2014
  9. Junio C HamanoFeb 14, 2014
  10. Josef WolfFeb 14, 2014
  11. Duy NguyenFeb 15, 2014
  12. Ingo RohloffFeb 17, 2014
  13. Junio C HamanoFeb 18, 2014
  14. John KeepingFeb 18, 2014
  15. Junio C HamanoFeb 18, 2014
  16. John KeepingFeb 18, 2014
  17. Michael HaggertyFeb 20, 2014
  18. Junio C HamanoFeb 20, 2014
  19. David KastrupFeb 18, 2014
  20. Junio C HamanoFeb 18, 2014
  21. Duy NguyenMar 23, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.