From: Greg Price <price@ksplice.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Stephen Haberman <stephen@exigencecorp.com>
Subject: Re: [PATCH] Fix rebase -p --onto
Date: Fri, 17 Jul 2009 15:00:44 -0400 [thread overview]
Message-ID: <20090717190043.GM7878@vinegar-pot.mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0907172029230.4495@intel-tinevez-2-302>
On Fri, Jul 17, 2009 at 08:32:20PM +0200, Johannes Schindelin wrote:
> > 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).
Understood. The -p functionality is invaluable already without -i,
and reordering commits with -p raises substantial new questions about
what the behavior should be.
I wonder if it might be worth giving an error message when the user
attempts to reorder commits under -p? The current behavior is
surprising (reordering A after B, C, D causes B, C, D to be dropped)
even when no merges are involved. I wouldn't want to give an error on
just the combination of options -i -p, though, since "edit" is useful.
> 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.
That would be excellent. I'm using git-sequencer from Stephan Beyer's
seq-builtin-dev branch for some work because I need this kind of
functionality. It would be great to see it in mainline in one form or
another. I don't doubt that it will require a good deal of work.
Thanks!
Greg
next prev parent reply other threads:[~2009-07-17 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 23:00 [PATCH] Fix rebase -p --onto Greg Price
2009-07-17 6:38 ` Johannes Sixt
2009-07-17 8:27 ` Junio C Hamano
2009-07-17 8:40 ` Johannes Sixt
2009-07-17 8:47 ` Johannes Sixt
2009-07-17 16:48 ` Greg Price
2009-07-17 18:32 ` Johannes Schindelin
2009-07-17 19:00 ` Greg Price [this message]
2009-07-17 16:33 ` Greg Price
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=20090717190043.GM7878@vinegar-pot.mit.edu \
--to=price@ksplice.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=stephen@exigencecorp.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).