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

Re: [PATCH 1/3] rebase -i: handle --continue more like non-interactive rebase

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 12, 2007, 22:26 UTC
Message-ID
<20070712222640.GA30532@steel.home>
In-Reply-To
<Pine.LNX.4.64.0707080300440.4093@racer.site>
Johannes Schindelin, Sun, Jul 08, 2007 04:01:29 +0200:
> Non-interactive rebase requires the working tree to be clean, but
> applies what is in the index without requiring the user to do it
> herself.  Imitate that, but (since we are interactive, after all)
> fire up an editor with the commit message.

Could we also have "git rebase <base> <branch>"? I find it useful when I have many branches to rebase:

    ~/project @master$ git rebase master branch1
    ~/project @branch1$ git rebase master branch2
    ~/project @branch2$ git rebase master branch3
    ...

Otherwise one have to, for example, "git checkout branch1" first, and only then run rebase-interactive. Checkout is not very pleasant operation on windows if you have many files (well, nothing is pleasant there, but this one have to be done often). Rebase-interactive is *very* slow there, but I just could not part with it after having tried it once :)

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 9 in “rebase -i: handle --continue more like non-interactive rebase”
  1. 1/3 rebase -i: handle --continue more like non-interactive rebaseJohannes Schindelin, Jul 8, 2007
  2. Johannes SchindelinJul 8, 2007
  3. Alex RiesenJul 12, 2007
  4. Johannes SchindelinAug 1, 2007
  5. Alex RiesenAug 1, 2007
  6. rebase -i: fix for optional [branch] parameterJohannes Schindelin, Aug 1, 2007
  7. Fix rebase interactive to allow specifying branch to rebase along with the baseAlex Riesen, Aug 1, 2007
  8. Johannes SchindelinAug 1, 2007
  9. Alex RiesenAug 1, 2007

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.