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

one half of a rebase

From
Geoffrey Irving <irving@naml.us>
Date
Sep 11, 2009, 17:25 UTC
Message-ID
<7f9d599f0909111025q42e3cdc6vba602b84c1d81215@mail.gmail.com>
If I'm on branch topic and do "git rebase master", git performs two operations:
1. Rewind the current head to master.
2. For each commit in topic that isn't in master, cherry pick it onto
the current head.

I would like to be able to do (2) as a separate operation. For example, if I start out on branch master and want to get all of topic's commits on top of the current head, I currently do

    git checkout topic
    git rebase master
    git branch -d master
    git branch -m master
If I could do (2) as a separate operation, it would look something like
    git cherry-pick-all topic

which is simpler and faster since it avoids switching files back and forth (master to topic and back). Is there a robust way to achieve the cherry-pick-all semantics with current commands? If not, how difficult would it be to partition rebase accordingly?

Thanks, Geoffrey

Next: Matthieu Moy
Message 1 of 5 in “one half of a rebase”
  1. Geoffrey IrvingSep 11, 2009
  2. Matthieu MoySep 11, 2009
  3. Alex RiesenSep 11, 2009
  4. Geoffrey IrvingSep 12, 2009
  5. Paolo BonziniSep 12, 2009

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.