From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to interactively rebase-and-reword nth commit?
Date: Wed, 25 Aug 2021 19:32:24 +0300 [thread overview]
Message-ID: <b1c62f6aa1eb06b64ee095dff23709a42d25cb16.camel@yandex.ru> (raw)
In-Reply-To: <CAN0heSoxE8zjzbYqRY6zvva=GEXEWx1k8FGhJMCf6N=pEcpZFw@mail.gmail.com>
Amazing, thank you, simple replacing EDITOR with GIT_SEQUENCE_EDITOR worked for
me!
On Wed, 2021-08-25 at 17:54 +0200, Martin Ågren wrote:
> Hi Konstantin,
>
> On Wed, 25 Aug 2021 at 16:07, Konstantin Kharlamov <hi-angel@yandex.ru> wrote:
> > I'm almost happy with `rebase-at`, except I don't know of any way to make it
> > work
> > with `reword` git action. You see, "rewording a commit" requires to run
> > EDITOR twice:
> > first to substitute `pick` with `reword`, and then to actually edit the
> > commit
> > message. But since EDITOR was substituted with sed, the 2nd run won't give
> > you an
> > actual editor to change the commit message.
>
> I think GIT_SEQUENCE_EDITOR is for pretty much exactly such a use-case:
>
> This environment variable overrides the configured Git editor when
> editing the todo list of an interactive rebase. See also git-
> rebase(1) and the sequence.editor option in git-config(1).
>
> Does that help, by not stomping on EDITOR/GIT_EDITOR?
>
> Martin
next prev parent reply other threads:[~2021-08-25 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 14:06 How to interactively rebase-and-reword nth commit? Konstantin Kharlamov
2021-08-25 15:01 ` Ævar Arnfjörð Bjarmason
2021-08-25 15:54 ` Martin Ågren
2021-08-25 16:32 ` Konstantin Kharlamov [this message]
2021-08-26 6:28 ` ZheNing Hu
2021-08-27 2:04 ` Jeff King
2021-08-27 9:18 ` 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=b1c62f6aa1eb06b64ee095dff23709a42d25cb16.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
/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 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 NNTP newsgroup(s).