From: Niko Mauno <niko.mauno@vaisala.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
quentin.schulz@theobroma-systems.com,
openembedded-core@lists.openembedded.org
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [OE-core] [PATCH] ref-manual: Fix invalid feature name
Date: Tue, 21 Feb 2023 12:32:47 +0200 [thread overview]
Message-ID: <c79a36ea-aada-ddef-be2c-e981782901a3@vaisala.com> (raw)
In-Reply-To: <14a72505-0e05-6b81-ce33-580cf986c898@bootlin.com>
On 20.2.2023 19.45, Michael Opdenacker wrote:
>
> Thanks for the patch!
> You also have an issue with the way your e-mails are received here. Here
> is a workaround:
> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Fixing_your_From_identity
>
> I fixed the commit manually, but doing this will help for next time.
Thanks for pointing the issue Michael, I've now applied the mitigation.
BR, Niko
prev parent reply other threads:[~2023-02-21 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230219143133.66511-1-niko.mauno@vaisala.com>
2023-02-20 9:20 ` [OE-core] [PATCH] ref-manual: Fix invalid feature name Quentin Schulz
2023-02-20 17:45 ` Michael Opdenacker
2023-02-21 10:32 ` Niko Mauno [this message]
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=c79a36ea-aada-ddef-be2c-e981782901a3@vaisala.com \
--to=niko.mauno@vaisala.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@theobroma-systems.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox