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

Octopus? Really? Interesting...

From
Jon Loeliger <jdl@freescale.com>
Date
Jan 4, 2008, 18:28 UTC
Message-ID
<1199471321.3133.22.camel@ld0161-tx32>
Guys,

So, I brain-wedged a merge here just now and was surprised to see that a simple fetch-n-merge yielded an octopus merge. I was expecting a fast-forward. So I went back and reviewed. What actually happend was this:

    $ git checkout master
    $ git fetch origin
    # check it out... looks great ... let's merge it
    $ git merge master origin/master
    merge performed by octopus.
Oh, yeah.  Duh.  I did name two branches.  Feh.
Couple questions:
    Is it ever NOT the case, that if you are on one
    branch ("master") and name it as a "to be merged"
    branch along with some others, that we can simplify
    the request by noting that it is the same as the
    current "to be merged into" target branch?
    Other than creating a log message with "merged
    by octopus", will this merge be content-identical
    to the obvious simplified merge?

Thanks, jdl

Next: Junio C Hamano
Message 1 of 2 in “Octopus? Really? Interesting...”
  1. Jon LoeligerJan 4, 2008
  2. Junio C HamanoJan 4, 2008

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.