All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [RFE] Allow for "interactive"-like actions in non-interactive rebase
Date: Mon, 6 May 2019 13:30:03 -0700	[thread overview]
Message-ID: <20190506203003.GA85211@google.com> (raw)
In-Reply-To: <1556895855.30374.0@yandex.ru>

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

  reply	other threads:[~2019-05-06 20:30 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 [this message]
2019-05-06 22:25   ` Eric Sunshine
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190506203003.GA85211@google.com \
    --to=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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.