All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] add basic b4 config file
@ 2025-09-05 12:29 Quentin Schulz
  2025-10-01  9:09 ` Hans Verkuil
  0 siblings, 1 reply; 8+ messages in thread
From: Quentin Schulz @ 2025-09-05 12:29 UTC (permalink / raw)
  To: linux-media; +Cc: Quentin Schulz

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?
---
 .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,
-- 
Quentin Schulz <quentin.schulz@cherry.de>


^ permalink raw reply related	[flat|nested] 8+ messages in thread
* [PATCH] add basic b4 config file
@ 2025-01-23 14:31 Quentin Schulz
  0 siblings, 0 replies; 8+ messages in thread
From: Quentin Schulz @ 2025-01-23 14:31 UTC (permalink / raw)
  To: docs; +Cc: Quentin Schulz

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.

Because we do not have anything to check for now, disable needs-checking
so patches can be sent without running b4 prep --check.

Because we do not have any auto-to-cc support (and the implicit one
using scripts/get_maintainer.pl cannot work for us), also disable
needs-auto-to-cc so patches can be sent without running b4 prep
--auto-to-cc.

[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>
---
I'm wondering if we couldn't add some per-patch check as well, checking
that the documentation builds for each for example. Could be added in a
later patch though. Any idea?
---
 .b4-config | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.b4-config b/.b4-config
new file mode 100644
index 0000000000000000000000000000000000000000..4f87f61b58519862da44fd9af6e6d0018edc7dc2
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,3 @@
+[b4]
+  send-series-cc = docs@lists.yoctoproject.org
+  prep-pre-flight-checks = disable-needs-auto-to-cc, disable-needs-checking

---
base-commit: 6b44257874858db3aa426d3e84a79c41cb4937a3
change-id: 20240524-b4-support-d5e749251bba

Best regards,
-- 
Quentin Schulz <quentin.schulz@cherry.de>



^ permalink raw reply related	[flat|nested] 8+ messages in thread
* [PATCH] add basic b4 config file
@ 2025-01-17 11:59 Quentin Schulz
  0 siblings, 0 replies; 8+ messages in thread
From: Quentin Schulz @ 2025-01-17 11:59 UTC (permalink / raw)
  To: openembedded-core; +Cc: Quentin Schulz

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.

Because we do not have anything to check for now, disable needs-checking
so patches can be sent without running b4 prep --check.

Because we do not have any auto-to-cc support (and the implicit one
using scripts/get_maintainer.pl cannot work for us), also disable
needs-auto-to-cc so patches can be sent without running b4 prep
--auto-to-cc.

[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>
---
Note that this file should be overridden by the one that I'll send for
poky by the merging script (no clue how that would work), i.e. an update
of .b4-config from OE-Core should not override the one from poky OE-Core
when we merge/cherry-pick OE-Core patches later on.
---
 .b4-config | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.b4-config b/.b4-config
new file mode 100644
index 0000000000000000000000000000000000000000..8ec5ddd91e1da05f27a53ff6f3d7351317461859
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,3 @@
+[b4]
+  send-series-cc = openembedded-core@lists.openembedded.org
+  prep-pre-flight-checks = disable-needs-auto-to-cc, disable-needs-checking

---
base-commit: ba492417cf8712ca8009154cfadeb494c1a6064f
change-id: 20250117-b4-support-10de313f53b7

Best regards,
-- 
Quentin Schulz <quentin.schulz@cherry.de>



^ permalink raw reply related	[flat|nested] 8+ messages in thread
* [PATCH] add basic b4 config file
@ 2024-09-26 15:14 Quentin Schulz
  2024-09-30 16:24 ` Jon Mason
  0 siblings, 1 reply; 8+ messages in thread
From: Quentin Schulz @ 2024-09-26 15:14 UTC (permalink / raw)
  To: meta-arm; +Cc: Quentin Schulz

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. Let's start without
it for now.

[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>
---
Support b4 for easier contribution workflow.

Note that this should be backportable as is to earlier releases.

Additionally, we may want to add:

send-prefixes = <insert release name>

in earlier release branches so that one doesn't even have to think about
adding the branch name when writing patches for older releases (added
bonus is that the maintainers would then know if someone has sent
patches developed on earlier releases instead of targeting master :) ).
---
 .b4-config | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.b4-config b/.b4-config
new file mode 100644
index 00000000..752ca4b2
--- /dev/null
+++ b/.b4-config
@@ -0,0 +1,2 @@
+[b4]
+	send-series-to = meta-arm@lists.yoctoproject.org

---
base-commit: ea2c1ab5db4e2bd9ad0e93534f62391c86417a0c
change-id: 20240926-b4-b6beffc1263b

Best regards,
-- 
Quentin Schulz <quentin.schulz@cherry.de>



^ permalink raw reply related	[flat|nested] 8+ messages in thread
* [PATCH] add basic b4 config file
@ 2024-05-24 13:49 Quentin Schulz
  0 siblings, 0 replies; 8+ messages in thread
From: Quentin Schulz @ 2024-05-24 13:49 UTC (permalink / raw)
  To: bitbake-devel; +Cc: Quentin Schulz

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>



^ permalink raw reply related	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2025-10-01 12:49 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-05 12:29 [PATCH] add basic b4 config file Quentin Schulz
2025-10-01  9:09 ` Hans Verkuil
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

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.