From: Eric Sunshine <sunshine@sunshineco.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Konstantin Kharlamov <hi-angel@yandex.ru>,
Git List <git@vger.kernel.org>
Subject: Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase
Date: Mon, 6 May 2019 18:25:22 -0400 [thread overview]
Message-ID: <CAPig+cTC8aGkM3ksG9cEapz33-FcjsvoO9ejeJzjmkyXHjvoJQ@mail.gmail.com> (raw)
In-Reply-To: <20190506203003.GA85211@google.com>
On Mon, May 6, 2019 at 4:30 PM Emily Shaffer <emilyshaffer@google.com> wrote:
> On Fri, May 03, 2019 at 06:04:15PM +0300, Konstantin Kharlamov wrote:
> > Interactive rebase (i.e. for example "git rebase -i HEAD~10") is used most
> > often to apply an action to a single commit, e.g. "rename", "edit", "fixup",
> > etc…
> >
> > Instead, it would be nice to have native support in git to start "rebase"
> > for a given commit, and pass the "interactive action" to use on that commit.
> >
> > $ git rebase -i HEAD~10 --action edit
> > $ git rebase -i HEAD~10 --action rename
> > $ git rebase -i HEAD~10 --action fixup
>
> I would totally use this. The equivalent workflow right now is a pretty
> large number of steps for, say, fixing a typo.
Isn't this pretty much what Phil Hord's RFC patch series[1] was about?
However, Junio outlined[2] a generalization of that approach providing
more flexibility and control.
[1]: https://public-inbox.org/git/20190422000712.13584-1-phil.hord@gmail.com/
[2]: https://public-inbox.org/git/xmqqk1fm9712.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2019-05-06 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 15:04 [RFE] Allow for "interactive"-like actions in non-interactive rebase Konstantin Kharlamov
2019-05-06 20:30 ` Emily Shaffer
2019-05-06 22:25 ` Eric Sunshine [this message]
2019-05-07 0:02 ` Konstantin Kharlamov
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cTC8aGkM3ksG9cEapz33-FcjsvoO9ejeJzjmkyXHjvoJQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=hi-angel@yandex.ru \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).