From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <foss+yocto@0leil.net>
Cc: yocto-patches@lists.yoctoproject.org,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients
Date: Thu, 11 Jun 2026 08:48:22 -0400 [thread overview]
Message-ID: <aiqulowvm9FN-Wug@localhost.localdomain> (raw)
In-Reply-To: <20260608-to-cc-v1-2-a1e3e7462875@cherry.de>
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
>
next prev parent reply other threads:[~2026-06-11 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 10:47 [PATCH wic 0/2] README.md: add single git command as example + add Trevor in Cc Quentin Schulz
2026-06-08 10:47 ` [PATCH wic 1/2] README.md: add example instruction for sending patches Quentin Schulz
2026-06-08 10:47 ` [PATCH wic 2/2] README.md: add Trevor (the maintainer)'s mail as Cc recipients Quentin Schulz
2026-06-11 12:48 ` Trevor Woerner [this message]
2026-06-11 13:08 ` Quentin Schulz
2026-06-11 12:54 ` Trevor Woerner
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=aiqulowvm9FN-Wug@localhost.localdomain \
--to=twoerner@gmail.com \
--cc=foss+yocto@0leil.net \
--cc=quentin.schulz@cherry.de \
--cc=yocto-patches@lists.yoctoproject.org \
/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.