git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase

From
KKKonstantin Kharlamov <hi-angel@yandex.ru>
Date
May 7, 2019, 00:02 UTC
Message-ID
<1557187347.2481.0@yandex.ru>
In-Reply-To
<CAPig+cTC8aGkM3ksG9cEapz33-FcjsvoO9ejeJzjmkyXHjvoJQ@mail.gmail.com>

On Пн, May 6, 2019 at 18:25, Eric Sunshine <sunshine@sunshineco.com> wrote:

Show 31 quoted lines
> 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.
Previous: Eric Sunshine
Message 4 of 4 in “[RFE] Allow for "interactive"-like actions in non-interactive rebase”
  1. Konstantin KharlamovMay 3, 2019
  2. Emily ShafferMay 6, 2019
  3. Eric SunshineMay 6, 2019
  4. Konstantin KharlamovMay 7, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.