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

Re: Now what: multiple HEAD refs

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 15, 2005, 15:40 UTC
Message-ID
<Pine.LNX.4.63.0512151638260.3104@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<81b0412b0512150654o49e1edacu67b88df6347736d2@mail.gmail.com>
Hi,
On Thu, 15 Dec 2005, Alex Riesen wrote:
> > 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?

No, it is not correct. To pull means that you want to merge the fetched ref (your ref1), and store the result in the current branch.

But if you write "ref1:HEAD", you pretend that you want to fast-forward the local branch "HEAD" to ref1, and get an error if it is not forwardable.

In your case, I guess, "git pull ref1" is what you meant.

Hth, Dscho

Previous: Alex RiesenNext: Alex Riesen
Message 8 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.