From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: Non-interactively rewording commit messages
Date: Thu, 30 Jun 2022 21:17:38 +0000 [thread overview]
Message-ID: <Yr4S8jHKbtuBuT1z@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <20220630152757.yxwhijvj5xoosrws@meerkat.local>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
On 2022-06-30 at 15:27:57, Konstantin Ryabitsev wrote:
> Hello, all:
>
> What's the best approach to non-interactively rewrite specific commit
> messages? In this particular case, I am trying to automatically retrieve code
> review trailers sent to the mailing list and put them into corresponding
> commits.
>
> For example, I have a set of commits:
>
> abcabc: This commit does foo
> bcdbcd: This commit does bar
> cdecde: This commit does baz
>
> They were all sent to the mailing list and a maintainer sent a "Reviewed-by"
> to the second commit. In a usual interactive rebase session this would be:
>
> pick abcabc
> reword bcdbcd
> pick cdecde
You can set GIT_SEQUENCE_EDITOR to a command which does this in-place on
the file...
> When the edit screen comes up for the bcdbcd commit, the author would manually
> stick the new trailer into the commit message. However, I can automate all
> that away with b4 -- just need a sane strategy for non-interactively rewriting
> entire commit messages at arbitrary points in the recent history.
...and you can set GIT_EDITOR to modify the commit message in-place in
whatever way you want, and then use git rebase -i to rebase.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-06-30 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 15:27 Non-interactively rewording commit messages Konstantin Ryabitsev
2022-06-30 17:32 ` Carlo Marcelo Arenas Belón
2022-06-30 17:34 ` Christian Couder
2022-06-30 17:54 ` Konstantin Ryabitsev
2022-06-30 18:10 ` Ævar Arnfjörð Bjarmason
2022-06-30 21:35 ` Junio C Hamano
2022-07-01 11:10 ` Christian Couder
2022-06-30 21:17 ` brian m. carlson [this message]
2022-07-01 4:01 ` Elijah Newren
2022-07-01 18:18 ` Konstantin Ryabitsev
2022-07-01 13:37 ` Johannes Schindelin
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=Yr4S8jHKbtuBuT1z@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
/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).