All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "Hart, Darren" <darren.hart@intel.com>, yocto <yocto@yoctoproject.org>
Subject: Re: poky-extras
Date: Fri, 28 Jun 2013 13:57:03 +0100	[thread overview]
Message-ID: <1372424223.9930.257.camel@ted> (raw)
In-Reply-To: <51CD86F1.7090409@windriver.com>

On Fri, 2013-06-28 at 08:52 -0400, Bruce Ashfield wrote:
> On 13-06-28 04:51 AM, Richard Purdie wrote:
> > Hi Bruce/Darren,
> >
> > My attention was drawn to the existence of poky-extras. This was really
> > a short term gap filling repository and I think the time has come to
> > remove it. There are basically two chunks of code in there.
> >
> > The meta-linaro pieces in there haven't been touched in two years and
> > are therefore dead. I think we should delete them to alleviate any
> > confusion.
> >
> > The kernel pieces have been touched more recently. Some moved into the
> > core, mostly its just example boiler plate type code now. I think this
> > needs moving to a better named repository if its still wanted/useful, or
> > we delete it. I personally don't have a strong preference.
> >
> > Can someone take care of sorting this out?
> 
> I can take care of finding it a new home. I use the repo daily, and keep
> bumping it with examples with each new kernel update or release. I was
> working on some urlremapper code for the layer, to replace the old
> boiler plate "uncomment this" examples that are current in the recipes ..
> that work has been backgrounded, but I can pick it up again as part
> of relocating the changes.
> 
> I'm out of the office for the next week and a half, but can have a look
> after that. Does that timeframe work ?

Yes, its not urgent and I don't want to remove something people use. I
do think that this would better as a meta-yocto-kernel or something
similar. How about we simply rename it to that and delete meta-linaro
from it?

Cheers,

Richard




  reply	other threads:[~2013-06-28 12:57 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   ` Richard Purdie [this message]
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                           ` 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=1372424223.9930.257.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=darren.hart@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.