From: Michael Halstead <michael@yoctoproject.org>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "Hart, Darren" <darren.hart@intel.com>, yocto <yocto@yoctoproject.org>
Subject: Re: poky-extras
Date: Sun, 30 Jun 2013 22:33:07 -0700 [thread overview]
Message-ID: <51D11493.6030602@yoctoproject.org> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF52828@ORSMSX101.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
I can change the name shortly. Is there any reason to keep a read-only
copy available at the current location temporarily?
Michael Halstead
Yocto Project / Sys Admin
On 06/30/2013 10:19 PM, Rifenbark, Scott M wrote:
> Hi,
>
> I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
>
> I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
>
> Thanks,
> Scott
>
>> -----Original Message-----
>> From: Hart, Darren
>> Sent: Friday, June 28, 2013 10:08 PM
>> To: Richard Purdie
>> Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
>> Subject: Re: poky-extras
>>
>> On Fri, 2013-06-28 at 14:56 +0100, Richard Purdie wrote:
>>> On Fri, 2013-06-28 at 09:40 -0400, Bruce Ashfield wrote:
>>>> On 13-06-28 09:22 AM, Rifenbark, Scott M wrote:
>>>>> All I need is the name to make some initial changes.
>>>> Personally, I'm fine with 'meta-yocto-kernel'. Naming things is
>>>> never easy, so I won't agonize over whether or not an "extras"
>>>> should be on the end. But the name should be clear that it isn't
>>>> the main yocto kernel, it's just a few crappy bbappends that make
>>>> working with it locally easier for some :)
>>>>
>>>> So my only counter proposal is: meta-yocto-kernel-extras
>>>>
>>>> I'm going to de-crapify the bbappends so they are more useful, and
>>>> have started on that work, but haven't finished it yet.
>>> No strong feelings here. I just wiped out meta-linaro from there
>> (hoping
>>> Darren won't mind) and that checksums.ini file.
>> That's fine, I was just thinking about that last week when I saw Linaro
>> has a meta-linaro. That's where it belongs, so buh-bye. :-)
>>
>> --
>> Darren Hart
>> Intel Open Source Technology Center
>> Yocto Project - Technical Lead - Linux Kernel
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4516 bytes --]
next prev parent reply other threads:[~2013-07-01 5:33 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 ` Michael Halstead [this message]
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 ` poky-extras Rifenbark, Scott M
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=51D11493.6030602@yoctoproject.org \
--to=michael@yoctoproject.org \
--cc=darren.hart@intel.com \
--cc=scott.m.rifenbark@intel.com \
--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.