From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Quentin Schulz <foss+kernel@0leil.net>, linux-media@vger.kernel.org
Cc: Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH] add basic b4 config file
Date: Wed, 1 Oct 2025 11:09:51 +0200 [thread overview]
Message-ID: <8eec5b1a-9b57-48d2-94dc-0afdb3f942ed@kernel.org> (raw)
In-Reply-To: <20250905-b4-v1-1-2cdc261fd86d@cherry.de>
On 05/09/2025 14:29, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> b4[1] is a very nice tool for mail-based contribution. A config[2] file
> exists to set up a few defaults. We can use it to set the To recipients
> to always add, in our case the mailing list.
>
> This shouldn't be necessary if we had a script that b4 prep --auto-to-cc
> could call to find the mail address(es) to send to, à-la
> scripts/get_maintainer.pl from the kernel tree.
>
> This allows us to not have to look for the mailing list to send the
> patches to, just use b4 and you're all set.
>
> [1] https://pypi.org/project/b4/
> [2] https://b4.docs.kernel.org/en/latest/config.html
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
> Since that ML is also used for other repos than v4l-utils and I've seen
> a few people using [v4l-utils] as prefixes, should we add
>
> send-prefixes = v4l-utils
>
> to the config file as well?
Yes please.
I'm not sure I want to have this in v4l-utils, but if I do, then definitely with
that prefix.
When you post the new patch, please prefix it with v4l-utils as well.
Regards,
Hans
> ---
> .b4-config | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/.b4-config b/.b4-config
> new file mode 100644
> index 0000000000000000000000000000000000000000..31873a088f0b32c174363f8b56a54a976b87fb17
> --- /dev/null
> +++ b/.b4-config
> @@ -0,0 +1,2 @@
> +[b4]
> + send-series-to = linux-media@vger.kernel.org
>
> ---
> base-commit: fc46fc8771bff905204e7463ab03ed1f355436b1
> change-id: 20250905-b4-1e813446afa4
>
> Best regards,
next prev parent reply other threads:[~2025-10-01 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 12:29 [PATCH] add basic b4 config file Quentin Schulz
2025-10-01 9:09 ` Hans Verkuil [this message]
2025-10-01 12:49 ` Ricardo Ribalda Delgado
-- strict thread matches above, loose matches on Subject: below --
2025-01-23 14:31 Quentin Schulz
2025-01-17 11:59 Quentin Schulz
2024-09-26 15:14 Quentin Schulz
2024-09-30 16:24 ` Jon Mason
2024-05-24 13:49 Quentin Schulz
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=8eec5b1a-9b57-48d2-94dc-0afdb3f942ed@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=foss+kernel@0leil.net \
--cc=linux-media@vger.kernel.org \
--cc=quentin.schulz@cherry.de \
/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.