From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Philip Balister <philip@balister.org>,
Mariano Lopez <mariano.lopez@linux.intel.com>,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [RFC] Mark of upstream CVE patches
Date: Tue, 15 Dec 2015 17:13:26 +0000 [thread overview]
Message-ID: <1450199606.13505.79.camel@linuxfoundation.org> (raw)
In-Reply-To: <567044A7.8050505@balister.org>
On Tue, 2015-12-15 at 11:49 -0500, Philip Balister wrote:
> On 12/15/2015 11:37 AM, Richard Purdie wrote:
> > On Tue, 2015-12-15 at 11:30 -0500, Philip Balister wrote:
> > > I also suggest copying the
> > >
> > > https://lists.yoctoproject.org/listinfo/yocto-security
> > >
> > > list.
> >
> > and the architecture list, this is something that should apply to
> > more
> > than OE-Core ideally.
>
> I thought the exact same thing seconds after hitting send. I'll let
> the
> security and architecture people decide which list is best for
> discussion.
>
> What I do want to see is fewer discussions cross posted across many
> lists.
Agreed, right now I just want people to get thinking about the right
place for some of these discussions to happen too though.
I suspect the right place is architecture since we're likely going to
want to update the patch submission guidelines and reach a wide
audience with this. I believe Mariano will repost onto the architecture
list and anyone interested can join in there.
Cheers,
Richard
next prev parent reply other threads:[~2015-12-15 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 16:03 [RFC] Mark of upstream CVE patches Mariano Lopez
2015-12-15 16:26 ` Otavio Salvador
2015-12-15 16:30 ` Philip Balister
2015-12-15 16:37 ` Richard Purdie
2015-12-15 16:49 ` Philip Balister
2015-12-15 17:13 ` Richard Purdie [this message]
2015-12-15 17:17 ` Mariano Lopez
2015-12-16 9:03 ` Sona Sarmadi
2015-12-16 9:21 ` Burton, Ross
2016-01-04 18:25 ` Mariano Lopez
2016-01-04 20:17 ` [oe] " Benjamin Esquivel
2016-01-08 15:22 ` Mariano Lopez
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=1450199606.13505.79.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mariano.lopez@linux.intel.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=philip@balister.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox