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

Re: Now what: multiple HEAD refs

From
Alex Riesen <raa.lkml@gmail.com>
Date
Dec 15, 2005, 14:54 UTC
Message-ID
<81b0412b0512150654o49e1edacu67b88df6347736d2@mail.gmail.com>
In-Reply-To
<7vlkymph4f.fsf@assigned-by-dhcp.cox.net>
On 12/15/05, Junio C Hamano <junkio@cox.net> wrote:
Show 11 quoted lines
> >> >
> >> > $ 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 ;-).
> >
> > no, that I have remembered. What I constantly forget is the
> > space-vs-colon difference.
>
> That statement sounds as if "git pull . ref1:HEAD" makes some
> sense and you typed it without colon by mistake.  But it does
exactly.
> not make any sense to me; I am puzzled ... what are you trying
> to achieve with "git pull . ref1:HEAD"?
merge branch ref1 into current. Is that not a correct refspec?
Previous: Junio C HamanoNext: Johannes Schindelin
Message 7 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.