{"thread":{"id":"51028","subject":"[RFE] Allow for \"interactive\"-like actions in non-interactive rebase","startedAt":"2019-05-03T15:10:21Z","lastAt":"2019-05-07T00:02:33Z","messageCount":4,"participants":["Konstantin Kharlamov","Emily Shaffer","Eric Sunshine"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"374881","messageId":"1556895855.30374.0@yandex.ru","threadId":"51028","inReplyTo":null,"subject":"[RFE] Allow for \"interactive\"-like actions in non-interactive rebase","fromName":"Konstantin Kharlamov","fromEmail":"hi-angel@yandex.ru","sentAt":"2019-05-03T15:04:15Z","receivedAt":"2019-05-03T15:10:21Z","isPatch":false,"sender":{"key":"hi-angel@yandex.ru","avatar":null},"body":"Interactive rebase (i.e. for example \"git rebase -i HEAD~10\") is used \nmost often to apply an action to a single commit, e.g. \"rename\", \n\"edit\", \"fixup\", etc…\n\nAs result, people keep coming up with custom scripts and aliases for \nevery distinct action.\n\nInstead, it would be nice to have native support in git to start \n\"rebase\" for a given commit, and pass the \"interactive action\" to use \non that commit. Examples:\n\n$ git rebase -i HEAD~10 --action edit\n$ git rebase -i HEAD~10 --action rename\n$ git rebase -i HEAD~10 --action fixup\n\n\n"},{"id":"374957","messageId":"20190506203003.GA85211@google.com","threadId":"51028","inReplyTo":"1556895855.30374.0@yandex.ru","subject":"Re: [RFE] Allow for \"interactive\"-like actions in non-interactive rebase","fromName":"Emily Shaffer","fromEmail":"emilyshaffer@google.com","sentAt":"2019-05-06T20:30:03Z","receivedAt":"2019-05-06T20:30:11Z","isPatch":false,"sender":{"key":"nasamuffin@google.com","avatar":"https://avatars.githubusercontent.com/u/1606826?v=4"},"body":"Hi,\n\nOn Fri, May 03, 2019 at 06:04:15PM +0300, Konstantin Kharlamov wrote:\n> Interactive rebase (i.e. for example \"git rebase -i HEAD~10\") is used most\n> often to apply an action to a single commit, e.g. \"rename\", \"edit\", \"fixup\",\n> etc…\n> \n> As result, people keep coming up with custom scripts and aliases for every\n> distinct action.\n> \n> Instead, it would be nice to have native support in git to start \"rebase\"\n> for a given commit, and pass the \"interactive action\" to use on that commit.\n\nI would totally use this. The equivalent workflow right now is a pretty\nlarge number of steps for, say, fixing a typo.\n\n> Examples:\n> \n> $ git rebase -i HEAD~10 --action edit\n> $ git rebase -i HEAD~10 --action rename\n> $ git rebase -i HEAD~10 --action fixup\n\nIs there an alternative to any of these actions that can already be\ntaken individually? Or, another way of asking, were the interactive\nrebase commands based on some other Git command which could be pain to\ndo on many commits individually?\n\nEmily\n"},{"id":"374960","messageId":"CAPig+cTC8aGkM3ksG9cEapz33-FcjsvoO9ejeJzjmkyXHjvoJQ@mail.gmail.com","threadId":"51028","inReplyTo":"20190506203003.GA85211@google.com","subject":"Re: [RFE] Allow for \"interactive\"-like actions in non-interactive rebase","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2019-05-06T22:25:22Z","receivedAt":"2019-05-06T22:25:36Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Mon, May 6, 2019 at 4:30 PM Emily Shaffer <emilyshaffer@google.com> wrote:\n> On Fri, May 03, 2019 at 06:04:15PM +0300, Konstantin Kharlamov wrote:\n> > Interactive rebase (i.e. for example \"git rebase -i HEAD~10\") is used most\n> > often to apply an action to a single commit, e.g. \"rename\", \"edit\", \"fixup\",\n> > etc…\n> >\n> > Instead, it would be nice to have native support in git to start \"rebase\"\n> > for a given commit, and pass the \"interactive action\" to use on that commit.\n> >\n> > $ git rebase -i HEAD~10 --action edit\n> > $ git rebase -i HEAD~10 --action rename\n> > $ git rebase -i HEAD~10 --action fixup\n>\n> I would totally use this. The equivalent workflow right now is a pretty\n> large number of steps for, say, fixing a typo.\n\nIsn't this pretty much what Phil Hord's RFC patch series[1] was about?\nHowever, Junio outlined[2] a generalization of that approach providing\nmore flexibility and control.\n\n[1]: https://public-inbox.org/git/20190422000712.13584-1-phil.hord@gmail.com/\n[2]: https://public-inbox.org/git/xmqqk1fm9712.fsf@gitster-ct.c.googlers.com/\n"},{"id":"374971","messageId":"1557187347.2481.0@yandex.ru","threadId":"51028","inReplyTo":"CAPig+cTC8aGkM3ksG9cEapz33-FcjsvoO9ejeJzjmkyXHjvoJQ@mail.gmail.com","subject":"Re: [RFE] Allow for \"interactive\"-like actions in non-interactive rebase","fromName":"Konstantin Kharlamov","fromEmail":"hi-angel@yandex.ru","sentAt":"2019-05-07T00:02:27Z","receivedAt":"2019-05-07T00:02:33Z","isPatch":false,"sender":{"key":"hi-angel@yandex.ru","avatar":null},"body":"\n\nOn Пн, May 6, 2019 at 18:25, Eric Sunshine <sunshine@sunshineco.com> \nwrote:\n> On Mon, May 6, 2019 at 4:30 PM Emily Shaffer \n> <emilyshaffer@google.com> wrote:\n>>  On Fri, May 03, 2019 at 06:04:15PM +0300, Konstantin Kharlamov \n>> wrote:\n>>  > Interactive rebase (i.e. for example \"git rebase -i HEAD~10\") is \n>> used most\n>>  > often to apply an action to a single commit, e.g. \"rename\", \n>> \"edit\", \"fixup\",\n>>  > etc…\n>>  >\n>>  > Instead, it would be nice to have native support in git to start \n>> \"rebase\"\n>>  > for a given commit, and pass the \"interactive action\" to use on \n>> that commit.\n>>  >\n>>  > $ git rebase -i HEAD~10 --action edit\n>>  > $ git rebase -i HEAD~10 --action rename\n>>  > $ git rebase -i HEAD~10 --action fixup\n>> \n>>  I would totally use this. The equivalent workflow right now is a \n>> pretty\n>>  large number of steps for, say, fixing a typo.\n> \n> Isn't this pretty much what Phil Hord's RFC patch series[1] was about?\n> However, Junio outlined[2] a generalization of that approach providing\n> more flexibility and control.\n> \n> [1]: \n> https://public-inbox.org/git/20190422000712.13584-1-phil.hord@gmail.com/\n> [2]: \n> https://public-inbox.org/git/xmqqk1fm9712.fsf@gitster-ct.c.googlers.com/\n\nThanks, indeed it is. I replied on the corresponding emails.\n\n\n"}]}