[PATCH wic 0/2] README.md: add single git command as example + add Trevor in Cc

[PATCH wic 0/2] README.md: add single git command as example + add Trevor in Cc

[Quentin Schulz]

Provide an example on how to generate the patches correctly (I have not
tested this personally, I took the example from meta-perl in
meta-openembedded).

Add Trevor in the Cc recipients in README.md to match what b4 is
configured to do in .b4-config (as suggested by Trevor[1]).

[1] https://lore.kernel.org/yocto-patches/aiHUEFS-ucG_p3kV@localhost.localdomain/

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
Quentin Schulz (2):
      README.md: add example instruction for sending patches
      README.md: add Trevor (the maintainer)'s mail as Cc recipients

 README.md | 11 +++++++++++
 1 file changed, 11 insertions(+)
---
base-commit: 1f9e8c77c0494f51a58ed139497bbe1bde0898de
change-id: 20260608-to-cc-d92a307508e7

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

[PATCH wic 1/2] README.md: add example instruction for sending patches

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

Let's actually document how to properly generate patches for wic so the
contributor doesn't have to figure this out on their own.

The git-send-email instruction wasn't tested, I just took it from
meta-perl from meta-openembedded and adapted it.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/README.md b/README.md
index c6fed66..0066ae4 100644
--- a/README.md
+++ b/README.md
@@ -57,6 +57,13 @@ When sending patches, please make sure the email subject line includes
 "[wic][PATCH]" and follow The Yocto Project community's patch submission
 guidelines.
 
+When generating the patches manually, this will generate what's expected:
+
+   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --subject-prefix='wic][PATCH'
+
+Nothing, except running `b4 send` to actually send the patches, needs to be done
+when using [b4](https://b4.docs.kernel.org/).
+
 ## Licensing
 
 GPL-2.0-only to match the original OpenEmbedded wic tooling.

-- 
2.54.0

[PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients

[Quentin Schulz]

From: Quentin Schulz <quentin.schulz@cherry.de>

The instructions now match with the .b4-config file.

Suggested-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0066ae4..3259019 100644
--- a/README.md
+++ b/README.md
@@ -57,9 +57,13 @@ When sending patches, please make sure the email subject line includes
 "[wic][PATCH]" and follow The Yocto Project community's patch submission
 guidelines.
 
+The patches should be sent with the mailing list (yocto-patches@lists.yoctoproject.org)
+in the To: recipients and the maintainer address (twoerner@gmail.com) in Cc:
+recipients.
+
 When generating the patches manually, this will generate what's expected:
 
-   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --subject-prefix='wic][PATCH'
+   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --cc twoerner@gmail.com --subject-prefix='wic][PATCH'
 
 Nothing, except running `b4 send` to actually send the patches, needs to be done
 when using [b4](https://b4.docs.kernel.org/).

-- 
2.54.0

Re: [PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients

[Trevor Woerner]

On Mon 2026-06-08 @ 12:47:59 PM, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The instructions now match with the .b4-config file.

Sort of... I believe the b4 emails will read: "[PATCH wic]" while the
cmdline emails will read: "[wic][PATCH]". No biggie, I'll find them
either way.

> Suggested-by: Trevor Woerner <twoerner@gmail.com>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>  README.md | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)

Applied to wic, master branch. Thanks!

> 
> diff --git a/README.md b/README.md
> index 0066ae4..3259019 100644
> --- a/README.md
> +++ b/README.md
> @@ -57,9 +57,13 @@ When sending patches, please make sure the email subject line includes
>  "[wic][PATCH]" and follow The Yocto Project community's patch submission
>  guidelines.
>  
> +The patches should be sent with the mailing list (yocto-patches@lists.yoctoproject.org)
> +in the To: recipients and the maintainer address (twoerner@gmail.com) in Cc:
> +recipients.
> +
>  When generating the patches manually, this will generate what's expected:
>  
> -   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --subject-prefix='wic][PATCH'
> +   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --cc twoerner@gmail.com --subject-prefix='wic][PATCH'

If my understanding is correct, in markdown, in order for this to be
offset as a proper code block, it would need to be indented 4 spaces,
not 3. Regardless this isn't relevant since we're not hosting (or
mirroring) this project on github, and the markdown renderer on
git.yoctoproject.org doesn't seem as in-sync with github's version of
markdown. Either 4 spaces, or wrapped in ``` delimiters.

In any case it doesn't look like the git.yoctoproject.org markdown
renderer understands ```bash blocks, so I'm posting a follow-up patch to
fix it all up.

>  Nothing, except running `b4 send` to actually send the patches, needs to be done
>  when using [b4](https://b4.docs.kernel.org/).
> 
> -- 
> 2.54.0
> 

Re: [PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients

[Trevor Woerner]

On Mon 2026-06-08 @ 12:47:59 PM, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> 
> The instructions now match with the .b4-config file.
> 
> Suggested-by: Trevor Woerner <twoerner@gmail.com>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
>  README.md | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)

Applied to wic, master branch (given the previous caveats). Thanks!

Re: [PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients

[Quentin Schulz]

Hi Trevor,

On 6/11/26 2:48 PM, Trevor Woerner wrote:
> On Mon 2026-06-08 @ 12:47:59 PM, Quentin Schulz wrote:
>> From: Quentin Schulz <quentin.schulz@cherry.de>
>>
>> The instructions now match with the .b4-config file.
> 
> Sort of... I believe the b4 emails will read: "[PATCH wic]" while the
> cmdline emails will read: "[wic][PATCH]". No biggie, I'll find them
> either way.
> 

Details, details :D

I believe this is actually supported by b4, via the b4.send-presubject 
configuration knob, only available since b4 v0.15 (end of March 2026). 
Distros probably aren't all shipping this version and if using an 
earlier version it probably will do nothing. And we don't want both 
otherwise we'll get [PATCH wic][wic] when using v0.15+?

>> Suggested-by: Trevor Woerner <twoerner@gmail.com>
>> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>> ---
>>   README.md | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
> 
> Applied to wic, master branch. Thanks!
> 
>>
>> diff --git a/README.md b/README.md
>> index 0066ae4..3259019 100644
>> --- a/README.md
>> +++ b/README.md
>> @@ -57,9 +57,13 @@ When sending patches, please make sure the email subject line includes
>>   "[wic][PATCH]" and follow The Yocto Project community's patch submission
>>   guidelines.
>>   
>> +The patches should be sent with the mailing list (yocto-patches@lists.yoctoproject.org)
>> +in the To: recipients and the maintainer address (twoerner@gmail.com) in Cc:
>> +recipients.
>> +
>>   When generating the patches manually, this will generate what's expected:
>>   
>> -   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --subject-prefix='wic][PATCH'
>> +   git send-email -M -1 --to yocto-patches@lists.yoctoproject.org --cc twoerner@gmail.com --subject-prefix='wic][PATCH'
> 
> If my understanding is correct, in markdown, in order for this to be
> offset as a proper code block, it would need to be indented 4 spaces,
> not 3. Regardless this isn't relevant since we're not hosting (or
> mirroring) this project on github, and the markdown renderer on
> git.yoctoproject.org doesn't seem as in-sync with github's version of
> markdown. Either 4 spaces, or wrapped in ``` delimiters.
> 

Markdown is a PITA, you never know what's supported by whatever parser 
is used. Going for the "original" Markdown is probably best, but who's 
gonna check if the syntax is proper for new patches?

> In any case it doesn't look like the git.yoctoproject.org markdown
> renderer understands ```bash blocks, so I'm posting a follow-up patch to
> fix it all up.
> 

It seems like it could via an extension, c.f. 
https://python-markdown.github.io/extensions/fenced_code_blocks/#syntax-highlighting 
(if Archwiki doesn't lie on what markdown formatter is used by cgit).

Thanks for the fixup!

Cheers,
Quentin