From: "VAUTRIN Emmanuel (Canal Plus Prestataire)" <Emmanuel.VAUTRIN@cpexterne.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>,
Khem Raj <raj.khem@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [meta-yocto][langdale][connman] Partial integration of CVE-2022-32293 fixes
Date: Wed, 15 Mar 2023 09:57:39 +0000 [thread overview]
Message-ID: <MRZP264MB154440CFE6C988CB0700C63793BF9@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAOSpxdam2mGY6BgHwdSMOdPQVfMWJfD7i3zd3uhUUKMraFKUKw@mail.gmail.com>
Thank you Steve for the answer.
> Thanks for bringing this to my attention.
> In the future please send this sort of thing to the openembedded-core
> mailing list. It would also be good to copy the author of the patch
> you are commenting on. (I've cc'd the openembedded-core list as wel
> as Khem)
I shall confess it was complicated to choose the relevant group. So, does
openembedded-core correspond to all sources in yocto/meta?
> Would you be willing to send a patch to the openembedded-core list
> that implements this regression fix?
Allright, I can do that, even if with my professional email the tabs are
automatically formatted as spaces, what corrupts the patches.
> Thanks!
> Steve
B.R.
Emmanuel
prev parent reply other threads:[~2023-03-15 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:16 [meta-yocto][langdale][connman] Partial integration of CVE-2022-32293 fixes VAUTRIN Emmanuel (Canal Plus Prestataire)
2023-03-14 17:25 ` [poky] " Alexander Kanavin
2023-03-14 17:25 ` Steve Sakoman
2023-03-15 9:57 ` VAUTRIN Emmanuel (Canal Plus Prestataire) [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=MRZP264MB154440CFE6C988CB0700C63793BF9@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM \
--to=emmanuel.vautrin@cpexterne.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@lists.yoctoproject.org \
--cc=raj.khem@gmail.com \
--cc=steve@sakoman.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).