* [RFE] Allow for "interactive"-like actions in non-interactive rebase
@ 2019-05-03 15:04 Konstantin Kharlamov
2019-05-06 20:30 ` Emily Shaffer
0 siblings, 1 reply; 4+ messages in thread
From: Konstantin Kharlamov @ 2019-05-03 15:04 UTC (permalink / raw)
To: Git List
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…
As result, people keep coming up with custom scripts and aliases for
every distinct action.
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. Examples:
$ git rebase -i HEAD~10 --action edit
$ git rebase -i HEAD~10 --action rename
$ git rebase -i HEAD~10 --action fixup
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase
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
0 siblings, 1 reply; 4+ messages in thread
From: Emily Shaffer @ 2019-05-06 20:30 UTC (permalink / raw)
To: Konstantin Kharlamov; +Cc: Git List
Hi,
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…
>
> As result, people keep coming up with custom scripts and aliases for every
> distinct action.
>
> 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.
I would totally use this. The equivalent workflow right now is a pretty
large number of steps for, say, fixing a typo.
> Examples:
>
> $ git rebase -i HEAD~10 --action edit
> $ git rebase -i HEAD~10 --action rename
> $ git rebase -i HEAD~10 --action fixup
Is there an alternative to any of these actions that can already be
taken individually? Or, another way of asking, were the interactive
rebase commands based on some other Git command which could be pain to
do on many commits individually?
Emily
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase
2019-05-06 20:30 ` Emily Shaffer
@ 2019-05-06 22:25 ` Eric Sunshine
2019-05-07 0:02 ` Konstantin Kharlamov
0 siblings, 1 reply; 4+ messages in thread
From: Eric Sunshine @ 2019-05-06 22:25 UTC (permalink / raw)
To: Emily Shaffer; +Cc: Konstantin Kharlamov, Git List
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase
2019-05-06 22:25 ` Eric Sunshine
@ 2019-05-07 0:02 ` Konstantin Kharlamov
0 siblings, 0 replies; 4+ messages in thread
From: Konstantin Kharlamov @ 2019-05-07 0:02 UTC (permalink / raw)
To: Eric Sunshine; +Cc: Emily Shaffer, Git List
On Пн, May 6, 2019 at 18:25, Eric Sunshine <sunshine@sunshineco.com>
wrote:
> 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/
Thanks, indeed it is. I replied on the corresponding emails.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-05-07 0:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2019-05-07 0:02 ` Konstantin Kharlamov
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).