From: Quentin Schulz <foss+yocto@0leil.net>
To: bitbake-devel@lists.openembedded.org
Cc: Quentin Schulz <quentin.schulz@cherry.de>
Subject: [PATCH] add basic b4 config file
Date: Fri, 24 May 2024 15:49:16 +0200 [thread overview]
Message-ID: <20240524-b4-support-v1-1-0c4334c36cc7@cherry.de> (raw)
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 Cc 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. While we could do
that, this opens the door to people trying to add a way to notify some
people (e.g. a MAINTAINERS file) which is not somewhere the project
wants to go right now, and this also makes sure the address is always
added even if one forgets to run b4 prep --auto-to-cc (which is part of
the typical workflow for U-Boot and Linux kernel, but is not necessary
thanks to this patch).
[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>
---
This adds a basic config file for b4 to avoid to have to add the mailing
list by hand. For documentation patches, one will still need to run
b4 send --cc docs@lists.yoctoproject.org
manually for sending it to the docs ML as well.
Note that b4 supports patchwork, c.f.
https://b4.docs.kernel.org/en/latest/config.html#patchwork-integration-settings
though I have no clue what it does with it as I am no maintainer, but
maybe something worth having a look at if some maintainer of this repo
wants to use b4 to merge stuff?
---
.b4-config | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.b4-config b/.b4-config
new file mode 100644
index 000000000..632e39db4
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,2 @@
+[b4]
+ send-series-cc = bitbake-devel@lists.openembedded.org
---
base-commit: ce166ae25793c11b0a190c531bef0c296fd74497
change-id: 20240524-b4-support-e9855fc54d40
Best regards,
--
Quentin Schulz <quentin.schulz@cherry.de>
next reply other threads:[~2024-05-24 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:49 Quentin Schulz [this message]
2024-05-24 15:18 ` [bitbake-devel] [PATCH] add basic b4 config file Khem Raj
2024-05-24 15:33 ` Quentin Schulz
2024-05-24 16:28 ` Khem Raj
2024-05-24 18:24 ` Tim Orling
2024-05-24 18:36 ` Tim Orling
2024-05-27 8:55 ` Quentin Schulz
2024-08-01 16:48 ` Kieran Bingham
2024-05-27 9:05 ` Quentin Schulz
-- strict thread matches above, loose matches on Subject: below --
2024-09-26 15:14 Quentin Schulz
2024-09-30 16:24 ` Jon Mason
2025-01-17 11:59 Quentin Schulz
2025-01-23 14:31 Quentin Schulz
2025-09-05 12:29 Quentin Schulz
2025-10-01 9:09 ` Hans Verkuil
2025-10-01 12:49 ` Ricardo Ribalda Delgado
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=20240524-b4-support-v1-1-0c4334c36cc7@cherry.de \
--to=foss+yocto@0leil.net \
--cc=bitbake-devel@lists.openembedded.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.