From: Michael Haggerty <mhagger@alum.mit.edu>
To: Jeff King <peff@peff.net>
Cc: git discussion list <git@vger.kernel.org>,
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: GSoC idea: allow "git rebase --interactive" todo lines to take options
Date: Thu, 27 Feb 2014 08:48:10 +0100 [thread overview]
Message-ID: <530EEDBA.6090804@alum.mit.edu> (raw)
In-Reply-To: <20140226105249.GE25711@sigill.intra.peff.net>
On 02/26/2014 11:52 AM, Jeff King wrote:
> On Wed, Feb 26, 2014 at 09:04:30AM +0100, Michael Haggerty wrote:
>
>> It would be nice to support more flexibility in the todo-list commands
>> by allowing the commands to take options. Maybe
>>
>> * Convert a commit into a merge commit:
>>
>> pick -p c0ffeee -p e1ee712 deadbab The oneline of the commit after
>
> This seems like a reasonable feature to me. All of your examples are
> possible with an "e"dit and another git command, but the convenience may
> be worth it (though personally, most of the examples you gave are
> particularly interesting to me[1]).
Don't forget that any of the parent commits might have been rewritten
due to the earlier lines of the rebase script. Rebase has to map the
specified SHA-1s to their new versions. So I don't think that this one
would be very practical to implement by hand.
Actually I think it is awkward to have to specify all of the parent
commits. I did it this way to make it look like commit-tree's -p
option. But any usage of this feature that *doesn't* include the
immediately preceding commit as a parent would probably be broken anyway
(for example, the preceding commit would become unreachable).
So maybe a better UI would be
pick --merge=e1ee712 deadbab The oneline of the commit after
(even though this precludes the short form "-m" because it is already
taken by --message).
On the other hand, allowing arbitrary parents with "-p" might be a way
to make "rebase --interactive" work half-sanely with parts of history
that *already* include merge commits. The todo list that rebase
prepares for the user would already include these "-p" lines.
What I like about allowing options in todo lists is that is that it
opens up a lot of possibilities for "git rebase --interactive" that, I
think, have previously been hampered by the restriction that commands
have to consist of a single word, and (until now) have to be abbreviable
to a single distinct letter.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2014-02-27 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:04 GSoC idea: allow "git rebase --interactive" todo lines to take options Michael Haggerty
2014-02-26 10:52 ` Jeff King
2014-02-26 11:14 ` Michael Haggerty
2014-02-26 11:42 ` Jeff King
2014-02-26 14:55 ` Tay Ray Chuan
2014-02-26 19:55 ` Junio C Hamano
2014-02-27 7:48 ` Michael Haggerty [this message]
2014-02-27 18:10 ` Brandon McCaig
2014-02-28 12:52 ` Jeff King
2014-02-28 14:03 ` Michael Haggerty
2014-03-11 1:37 ` Jeff King
2014-03-11 19:31 ` Junio C Hamano
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=530EEDBA.6090804@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=martin.von.zweigbergk@gmail.com \
--cc=peff@peff.net \
/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).