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

rebase vs rebase -i

From
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 4, 2010, 04:19 UTC
Message-ID
<76718491002032019i5f8ea947paa527988ddb7a378@mail.gmail.com>
Why does git rebase use format-patch + am, while rebase -i uses cherry-pick?
Just curious. In particular though, it seems especially odd in this case:
$ git rebase --onto <newbase> <upstream>
vs
$ env GIT_EDITOR=true git rebase -i --onto <newbase> <upstream>

Both in theory produce an identical end-result, while using two different implementations.

(Here I'm setting GIT_EDITOR=true just to demonstrate that I didn't change the list of commits in the latter case.)

j.
Next: Johannes Schindelin
Message 1 of 10 in “rebase vs rebase -i”
  1. Jay SoffianFeb 4, 2010
  2. Johannes SchindelinFeb 4, 2010
  3. Jay SoffianFeb 4, 2010
  4. Johannes SchindelinFeb 4, 2010
  5. Jay SoffianFeb 4, 2010
  6. Johannes SchindelinFeb 4, 2010
  7. Jay SoffianFeb 4, 2010
  8. Junio C HamanoFeb 5, 2010
  9. Junio C HamanoFeb 5, 2010
  10. Jay SoffianFeb 5, 2010

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.