From: Bugspray Bot <bugbot@kernel.org>
To: erik.schilling@linaro.org, konstantin@linuxfoundation.org,
tools@linux.kernel.org, bugs@lists.linux.dev
Subject: Re: Allow sending prefixes before [PATCH]
Date: Tue, 18 Nov 2025 20:40:25 +0000 (UTC) [thread overview]
Message-ID: <20251118-b217642c6-fcebc74d7e6d@bugzilla.kernel.org> (raw)
In-Reply-To: <CTPW75Q2ISUN.251ELTNP6RB22@fedora>
Antonin Godard writes in commit d7232f5db2e4379bd9372b00707a78ec8d36b44a:
Add support for setting a presubject
Some mailing lists require a prefix to come before the [PATCH] in the
subject of emails, such as OpenEmbedded or libgpiod. The current prefix
mechanism does not allow for that (only after PATCH), and setting the
format.subjectPrefix Git option does not work either.
Add a new configuration option send-presubject as well as a
--set-presubject argument to be able to include anything that should
come before the subject. The logic behind prefixes is not changed and
this new option does not break any existing prefix assignments.
In order not to break the logic in LoreSubject's __init__ function,
which parses the subject line and strips brackets in order to reorganize
the subject line later, the presubject must be enclosed with brackets
too (_check_presubject() is used to ensure that).
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217642
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=d7232f5db2e4)
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-11-18 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CTPW75Q2ISUN.251ELTNP6RB22@fedora>
2023-07-07 16:39 ` Allow sending prefixes before [PATCH] Kernel.org Bugbot
2025-10-16 7:30 ` Antonin Godard via Bugspray Bot
2025-11-10 10:20 ` Louis Rannou via Bugspray Bot
2025-11-17 8:45 ` Louis Rannou via Bugspray Bot
2025-11-18 20:40 ` Bugspray Bot [this message]
2025-11-28 9:55 ` Louis Rannou via Bugspray Bot
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=20251118-b217642c6-fcebc74d7e6d@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=erik.schilling@linaro.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.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).