3 Commits

Author	SHA1	Message	Date
Quentin Schulz	d2e7e6cb65	.b4-config: automatically add 2025.02.x prefix ... This avoids having to run b4 prep --set-prefixes 2025.02.x to add the 2025.02.x prefix to the patch subject. You do need b4 0.11+ to make use of that. Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Thomas Perale <thomas.perale@mind.be>	2026-04-15 12:51:47 +02:00
Brandon Maier	747c3ae005	.b4-config: check patches with ./utils/check-package ... NOTE: This requires `b4` version 0.14.2 or later as earlier versions had a bug that broke custom prep-perpatch-check-cmd[1]. If a check-cmd is declared, `b4` will warn developers to run the patch checker before sending a patch series[2][3]. Developers can then run `b4 prep --check` to automatically run ./utils/check-package on only files modified in the patch series. [1] 0741bc9a5b [2] https://b4.docs.kernel.org/en/latest/contributor/send.html#passing-pre-flight-checks-v0-14 [3] https://b4.docs.kernel.org/en/latest/config.html#contributor-oriented-settings Signed-off-by: Brandon Maier <brandon.maier@collins.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>	2025-02-04 18:44:39 +01:00
Brandon Maier	322213e131	.b4-config: configure b4 for Buildroot ... `b4` is a commandline tool to make patch-based development easier[1]. It is primarily used for Linux kernel development, but can be configured to support any project that has a public-inbox endpoint. Buildroot has a public-inbox mirror at "https://lore.kernel.org/buildroot/". We configure some basic settings that tell `b4` where to send patches and how to use get-developers. [1] https://b4.docs.kernel.org/en/latest/ Signed-off-by: Brandon Maier <brandon.maier@collins.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>	2024-07-14 22:35:10 +02:00