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

Re: RFC: git pull <remote> making an octopus?

From
MTMichael S. Tsirkin <mst@mellanox.co.il>
Date
Aug 17, 2006, 09:46 UTC
Message-ID
<20060817094647.GG2630@mellanox.co.il>
In-Reply-To
<7v1wrfu3tl.fsf@assigned-by-dhcp.cox.net>
Quoting r. Junio C Hamano <junkio@cox.net>:
> > No, I just reproduced this on plain 1.4.2.
> 
> Doesn't reproduce for me and I am getting worried.
No, that was my mistake, sorry about not clarifying that.
Basically what confused me was the following text in get-fetch manpage:
	While git-pull  run  without  any  explicit <refspec> parameter takes
	default <refspec>s from Pull: lines, it merges only  the  first
	<refspec> found into the current branch, after fetching all the remote
	refs.

And this actually applied to remotes in $GITDIR/remotes and not just when git-pull is run without any parameters.

-- 
MST
Previous: Alex Riesen
Message 10 of 10 in “RFC: git pull <remote> making an octopus?”
  1. Michael S. TsirkinAug 14, 2006
  2. Junio C HamanoAug 14, 2006
  3. Michael S. TsirkinAug 14, 2006
  4. Michael S. TsirkinAug 14, 2006
  5. Junio C HamanoAug 14, 2006
  6. Alex RiesenAug 15, 2006
  7. Junio C HamanoAug 15, 2006
  8. Junio C HamanoAug 17, 2006
  9. Alex RiesenAug 17, 2006
  10. Michael S. TsirkinAug 17, 2006

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.