From: Sinan Kaya <okaya@kernel.org>
To: akuster808 <akuster808@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [sumo] [meta-virtualization] [PATCH v1] docker: CVE-2018-10892
Date: Fri, 5 Oct 2018 12:02:02 -0400 [thread overview]
Message-ID: <c2ace759-e477-7d2c-05c4-9fe92b9cfd93@kernel.org> (raw)
In-Reply-To: <728619d5-f5bc-f0ed-a1ac-bc1ef905ae68@gmail.com>
On 10/5/2018 12:00 PM, akuster808 wrote:
> Sinan,
>
>
> On 10/05/2018 08:55 AM, Sinan Kaya wrote:
>> On 10/5/2018 11:41 AM, Bruce Ashfield wrote:
>>> Wrong list.
>>>
>>> This needs to go to the meta-virtualization mailing list.
>>
>> Thanks for the heads up. Is there a document somewhere saying which
>> patch needs to go to which list?
>
> Every Layer should have a README. That README should include where to
> send patches.
>
> |Maintenance ----------- Send pull requests, patches, comments or
> questions to meta-virtualization@yoctoproject.org Maintainer: Bruce
> Ashfield <bruce.ashfield@gmail.com> When sending single patches, please
> using something like: $ git send-email -1 -M --to
> meta-virtualization@yoctoproject.org
> --subject-prefix='meta-virtualization][PATCH' The mailing list you will
> need to subscribe to Hope this helps. - Armin |
>
>>
>> This is the second time I screwed up.
>
>
Got it. I just needed to know where to look.
next prev parent reply other threads:[~2018-10-05 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 3:47 [sumo] [meta-virtualization] [PATCH v1] docker: CVE-2018-10892 Sinan Kaya
2018-10-05 15:41 ` Bruce Ashfield
2018-10-05 15:55 ` Sinan Kaya
2018-10-05 16:00 ` akuster808
2018-10-05 16:02 ` Sinan Kaya [this message]
2018-10-05 16:33 ` [sumo] " Sinan Kaya
2018-10-10 3:20 ` Bruce Ashfield
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=c2ace759-e477-7d2c-05c4-9fe92b9cfd93@kernel.org \
--to=okaya@kernel.org \
--cc=akuster808@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.