From: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
To: "Hart, Darren" <darren.hart@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: poky-extras
Date: Mon, 1 Jul 2013 17:31:00 +0000 [thread overview]
Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF52B13@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <1372699690.18377.6.camel@envy.home>
I think the name is meta-yocto-kernel-extras. That is what I have pushed to the docs.
Scott
>-----Original Message-----
>From: Hart, Darren
>Sent: Monday, July 01, 2013 10:28 AM
>To: Richard Purdie
>Cc: Michael Halstead; Bruce Ashfield; Rifenbark, Scott M; yocto;
>Zanussi, Tom
>Subject: Re: poky-extras
>
>On Mon, 2013-07-01 at 07:46 +0100, Richard Purdie wrote:
>> On Sun, 2013-06-30 at 23:18 -0700, Michael Halstead wrote:
>> > On 06/30/2013 10:44 PM, Darren Hart wrote:
>> > > On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote:
>> > > > I can change the name shortly. Is there any reason to keep a
>read-only
>> > > > copy available at the current location temporarily?
>> > > Not really. Unless Bruce is using it in some automated scripts
>that need
>> > > to be updated.
>> > >
>> >
>> > The name has been changed. Shall we update the description or is
>> > "Supplementary metadata layers to extend the Poky core" still
>> > appropriate?
>>
>> We can change it to something like "Supplementary linux-yocto kernel
>> development metadata" unless Bruce has any better description.
>
>Bruce is out this week with limited email access. He isn't terribly
>picky on naming and that description should work as good as any.
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-07-01 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 8:51 poky-extras Richard Purdie
2013-06-28 12:52 ` poky-extras Bruce Ashfield
2013-06-28 12:57 ` poky-extras Richard Purdie
2013-06-28 13:02 ` poky-extras Bruce Ashfield
2013-06-28 13:22 ` poky-extras Rifenbark, Scott M
2013-06-28 13:40 ` poky-extras Bruce Ashfield
2013-06-28 13:49 ` poky-extras Rifenbark, Scott M
2013-06-28 13:56 ` poky-extras Richard Purdie
2013-06-29 5:08 ` poky-extras Darren Hart
2013-07-01 5:19 ` poky-extras Rifenbark, Scott M
2013-07-01 5:33 ` poky-extras Michael Halstead
2013-07-01 5:44 ` poky-extras Darren Hart
2013-07-01 6:18 ` poky-extras Michael Halstead
2013-07-01 6:46 ` poky-extras Richard Purdie
2013-07-01 17:28 ` poky-extras Darren Hart
2013-07-01 17:31 ` Rifenbark, Scott M [this message]
2013-07-03 2:26 ` poky-extras Bruce Ashfield
2013-07-03 2:24 ` poky-extras 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=41DEA4B02DBDEF40A0F3B6D0DDB123797FF52B13@ORSMSX101.amr.corp.intel.com \
--to=scott.m.rifenbark@intel.com \
--cc=darren.hart@intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@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.