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

Re: Now what: multiple HEAD refs

From
Junio C Hamano <junkio@cox.net>
Date
Dec 15, 2005, 09:29 UTC
Message-ID
<7v8xumr9mw.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<81b0412b0512150105p5bacd6a1j938824ae2ab96858@mail.gmail.com>
Alex Riesen <raa.lkml@gmail.com> writes:
> just a heads-up for everyone tried "git pull" after using "git merge" too much:
>
> $ git pull . ref1 HEAD (notice the space!)

If you were too used to git merge, you would have wrote HEAD before ref1, so that does not sound plausible ;-).

        $ git pull . maint HEAD
        error: no such remote ref refs/heads/HEAD
        Fetch failure: .
	$ echo $?
        1

But worse yet, the above syntax is to create an Octopus, and you probably did not mean that.

I think the reason why my trial here worked correctly while you had trouble with it is because I have the send-pack fix from Pasky last night.

Previous: Alex RiesenNext: Alex Riesen
Message 2 of 9 in “Now what: multiple HEAD refs”
  1. Alex RiesenDec 15, 2005
  2. Junio C HamanoDec 15, 2005
  3. Alex RiesenDec 15, 2005
  4. Junio C HamanoDec 15, 2005
  5. Alex RiesenDec 15, 2005
  6. Junio C HamanoDec 15, 2005
  7. Alex RiesenDec 15, 2005
  8. Johannes SchindelinDec 15, 2005
  9. Alex RiesenDec 15, 2005

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.