From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Junio C Hamano <gitster@pobox.com>,
Richard Peterson <richard@rcpeterson.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org
Subject: Re: git rebase --interactive commits order
Date: Sat, 14 May 2011 12:58:26 +0200 [thread overview]
Message-ID: <BANLkTinbHOD9AXycM1gXYab+P-PMwOxK6Q@mail.gmail.com> (raw)
In-Reply-To: <20110513175112.GA14079@vidovic>
> 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".
Yes, this is what has been suggested. Just display in reverse in the
editor, and on save read the tasks to be done in a reverse manner or
simply reverse the tasks to be done before processing normally.
In fact I can already implement it in my editor by reversing the
commits (vim, some command), doing my stuffs, then reversing it back
before saving. It's pretty error prone because if I forget to reverse
them back then bad things happen, so it'd be nice if rebase handled
this for me.
Philippe
next prev parent reply other threads:[~2011-05-14 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 9:30 git rebase --interactive commits order Philippe Vaucher
2011-05-09 10:10 ` David
2011-05-09 23:31 ` Steven E. Harris
2011-05-10 22:20 ` Philippe Vaucher
2011-05-10 22:30 ` Sverre Rabbelier
2011-05-10 23:26 ` Junio C Hamano
2011-05-11 15:43 ` Richard Peterson
2011-05-11 17:24 ` Junio C Hamano
2011-05-11 18:39 ` Richard Peterson
2011-05-11 18:45 ` Philippe Vaucher
2011-05-13 17:51 ` Nicolas Sebrecht
2011-05-14 10:58 ` Philippe Vaucher [this message]
2011-05-10 22:56 ` Junio C Hamano
2011-05-10 23:05 ` Philippe Vaucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinbHOD9AXycM1gXYab+P-PMwOxK6Q@mail.gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s.dev@gmx.fr \
--cc=richard@rcpeterson.com \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).