From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: Non-interactively rewording commit messages
Date: Thu, 30 Jun 2022 10:32:11 -0700 [thread overview]
Message-ID: <20220630173211.pnliwplmimcaygny@carlos-mbp-2.lan> (raw)
In-Reply-To: <20220630152757.yxwhijvj5xoosrws@meerkat.local>
On Thu, Jun 30, 2022 at 11:27:57AM -0400, Konstantin Ryabitsev wrote:
> just need a sane strategy for non-interactively rewriting
> entire commit messages at arbitrary points in the recent history.
assuming you are still doing it by calling (albeit programmatically):
rebase --autosquash -i
then you could prepare the new message by also programmatically doing
a `git commit --fixup reword:<commit>` IMHO
Carlo
next prev parent reply other threads:[~2022-06-30 17:32 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 [this message]
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
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=20220630173211.pnliwplmimcaygny@carlos-mbp-2.lan \
--to=carenas@gmail.com \
--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).