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

Re: git rebase --interactive commits order

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
May 13, 2011, 17:51 UTC
Message-ID
<20110513175112.GA14079@vidovic>
In-Reply-To
<7v39klgng7.fsf@alter.siamese.dyndns.org>
The 11/05/11, Junio C Hamano wrote:
Show 17 quoted lines
> Richard Peterson <richard@rcpeterson.com> writes:
> 
> > On Tue, May 10, 2011 at 7:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
> >>
> >> Devils lie in the details.  For example, should squash/fixup come before
> >> or after the squashed commit when --reverse is in effect, and why?
> >>
> >> Should "rebase --reverse --continue" work after it gets interrupted, if
> >> not why not?
> >
> > Yes, it should work,...
> 
> Of course, if you start with --reverse, it is clear and obvious that
> 'continue' should continue with the reversed instruction sheet, and it
> probabaly should take --reverse as a no-op when given with --continue.
> The original question should have been written more carefully to avoid
> soliciting the response that addresses that uninteresting case.
I don't understand. Why not just _display_ the commit in reverse order?

Then, from the user POV commands like squash, fixup, etc would apply in reverse order too (from up to down); keeping the mental model for "apply against ancestor".

-- 
Nicolas Sebrecht
Previous: Philippe VaucherNext: Philippe Vaucher
Message 11 of 14 in “git rebase --interactive commits order”
  1. Philippe VaucherMay 9, 2011
  2. DavidMay 9, 2011
  3. Steven E. HarrisMay 9, 2011
  4. Philippe VaucherMay 10, 2011
  5. Sverre RabbelierMay 10, 2011
  6. Junio C HamanoMay 10, 2011
  7. Richard PetersonMay 11, 2011
  8. Junio C HamanoMay 11, 2011
  9. Richard PetersonMay 11, 2011
  10. Philippe VaucherMay 11, 2011
  11. Nicolas SebrechtMay 13, 2011
  12. Philippe VaucherMay 14, 2011
  13. Junio C HamanoMay 10, 2011
  14. Philippe VaucherMay 10, 2011

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.