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

RFC: git pull <remote> making an octopus?

From
MTMichael S. Tsirkin <mst@mellanox.co.il>
Date
Aug 14, 2006, 06:43 UTC
Message-ID
<20060814064336.GE21963@mellanox.co.il>

Hi! If I do

$git pull origin

where origin is a file in .git/remotes/origin with multiple Pull: lines, then I seem to get an octopus merge. I would expect it to behave in the same way as git pull without parameters. Is this a bug or a feature?

My git pull page says:
              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. This is because making an Octopus from remote refs
              is rarely done, while keeping track of multiple remote heads  in
              one-go by fetching more than one is often useful.

So, the same logic seems to apply to anything under .git/remotes. Right?

-- 
MST
Next: Junio C Hamano
Message 1 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.