From: "Steven E. Harris" <seh@panix.com>
To: git@vger.kernel.org
Subject: Re: git rebase --interactive commits order
Date: Mon, 09 May 2011 19:31:20 -0400 [thread overview]
Message-ID: <m2d3jr1mev.fsf@Spindle.sehlabs.com> (raw)
In-Reply-To: BANLkTi=PyBfMxCbWNfJEXEP6-MphdeE+_Q@mail.gmail.com
David <bouncingcats@gmail.com> writes:
> I find I have to do a mental double check before every such operation.
I don't think I've /ever/ run "rebase -i" and gotten the order correct
on the first try. I have to note the oldest commit I expect to see, hunt
around for it in the list, orient myself to the sequence, then try to
rearrange things. Usually the rearrangement still winds up being in the
wrong order.
--
Steven E. Harris
next prev parent reply other threads:[~2011-05-09 23:31 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 [this message]
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=m2d3jr1mev.fsf@Spindle.sehlabs.com \
--to=seh@panix.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).