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

Re: [PATCH] Fix rebase -p --onto

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 17, 2009, 18:32 UTC
Message-ID
<alpine.DEB.1.00.0907172029230.4495@intel-tinevez-2-302>
In-Reply-To
<20090717164845.GL7878@vinegar-pot.mit.edu>
Hi,
On Fri, 17 Jul 2009, Greg Price wrote:
Show 14 quoted lines
> On Fri, Jul 17, 2009 at 10:40:08AM +0200, Johannes Sixt wrote:
> > I have used rebase -i -p in the past to rewrite history that involves
> > merges of topic branches like this:
> > 
> >   ---------Y--M--M--F     <-- master
> >              /  /
> >   ----a--a--a  /
> >               /
> >   --b--b--b--b
> > 
> > where F is a fixup that I want to insert between Y and M, and I thought
> > rebase -i -p was intended for this use-case.
> 
> I don't believe rebase -i -p has ever worked with reordering commits.

It was not meant to. Actually, it was never meant as "rebase -i -p", but always as "rebase -p" (which, for technical reasons, would be implemented in git-rebase--interactive.sh).

Having said that, I am working on a rebase-i-p series which _does_ allow reordering commits, putting commits on newly-created topic branches, redoing merges explicitely.

Unfortunately, I seem to have less and less time for Git (which is not helped by the frustrating experience of a first-slow then-failing GSoC project), and when I finally decided to set aside some time to polish the series and submit it, 1.6.4-rc0 came out. And I do not want Junio to be distracted from that very important (think push-to-current-branch) release.

Ciao, Dscho

Previous: Greg PriceNext: Greg Price
Message 7 of 9 in “Fix rebase -p --onto”
  1. Fix rebase -p --ontoGreg Price, Jul 16, 2009
  2. Johannes SixtJul 17, 2009
  3. Junio C HamanoJul 17, 2009
  4. Johannes SixtJul 17, 2009
  5. Johannes SixtJul 17, 2009
  6. Greg PriceJul 17, 2009
  7. Johannes SchindelinJul 17, 2009
  8. Greg PriceJul 17, 2009
  9. Greg PriceJul 17, 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.