git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: git@vger.kernel.org
Subject: git rebase --interactive commits order
Date: Mon, 9 May 2011 11:30:14 +0200	[thread overview]
Message-ID: <BANLkTimX2tupqV464+Re8u06TT+qRmqPuw@mail.gmail.com> (raw)

Hello,

I did try to find a similar topic in the archive, but couldn't so here I ask.

Is there an option or would it be possible to make it so that `git
rebase -i` lists commits in reverse chronological order, like it does
for `git log` ?

Almost every git commands I use lists events in reverse chronological
order (reflog, log, gitk) and then you do an interactive rebase and it
always takes me a second or two to switch mindsets and start reading
them in chronological order. I asked around and I'm far from being the
only one who think this is counter-intuitive. I understand there's an
implementation simplicity reason for it to be that way, and also that
it is somewhat logical to show the commits to be applied in order, but
as your mind is trained to read them in reverse chronological order
with the other commands I'd find it more consistant if rebase also
followed that.

Philippe

             reply	other threads:[~2011-05-09  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09  9:30 Philippe Vaucher [this message]
2011-05-09 10:10 ` git rebase --interactive commits order 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
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=BANLkTimX2tupqV464+Re8u06TT+qRmqPuw@mail.gmail.com \
    --to=philippe.vaucher@gmail.com \
    --cc=git@vger.kernel.org \
    /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).