From: Tom Zanussi <tom.zanussi@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
yocto-infrastructure@yoctoproject.org
Subject: Re: Bugzilla Re-organization
Date: Fri, 01 Jun 2012 16:47:20 -0500 [thread overview]
Message-ID: <1338587240.28421.13.camel@elmorro> (raw)
In-Reply-To: <4FC93751.4060606@linux.intel.com>
On Fri, 2012-06-01 at 14:42 -0700, Darren Hart wrote:
>
> On 06/01/2012 02:33 PM, Tom Zanussi wrote:
> > On Fri, 2012-06-01 at 10:45 -0700, Darren Hart wrote:
>
> >> The other Kernel related path would include
> >> Build System & Metadata
> >> Layers - OpenEmbedded-Core
> >> kernel
> >>
> >> This would be for the kernel.bbclass and other recipes and classes.
> >>
> >
> > It would be nice to have that fact reflected in the name somehow, to
> > avoid confusion for users with Yocto Project Components->Kernel, but I'm
> > not coming up with anything wieldy.
>
> kernel-recipes ?
>
It doesn't really capture the 'classes' part, but I suppose that would
be implied and close enough.
Tom
> >> So, the final layout would be:
> >>
> >> Yocto Project Components
> >> BSPs
> >> bsps-runtime
> >> bsps-configuration (these top too being "generic" buckets)
> >> bsps-meta-yocto
> >
> > On the other hand this naming is clean and consistent with the rest, so
> > is probably better.
>
> Ah, but you remind me that we probably also need:
>
> bsps-oe-core
>
> >
> >> bsps-meta-fsl-ppc
> >> bsps-meta-intel
> >> bsps-meta-ti
> >> bsps-tools
> >> bsps-xilinx (meta-xilinx?)
> >>
> >> Kernel
> >> linux-yocto
> >> kernel-configuration
> >> kernel-tooling
> >>
> >> I believe this would make it much easier for us to manage Kernel related
> >> issues across the project.
> >>
> >
> > I agree. Acked-by-me...
>
> Great. Michael, the kernel-team is now in agreement.
>
prev parent reply other threads:[~2012-06-01 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 22:38 Bugzilla Re-organization Michael Halstead
2012-05-28 5:28 ` Damian, Alexandru
2012-05-30 14:51 ` Rifenbark, Scott M
2012-05-30 15:12 ` Michael Halstead
2012-05-31 18:27 ` Darren Hart
2012-06-01 3:37 ` Bruce Ashfield
2012-06-01 17:43 ` Darren Hart
2012-06-01 20:03 ` Bruce Ashfield
2012-06-01 17:45 ` Darren Hart
2012-06-01 21:33 ` Tom Zanussi
2012-06-01 21:42 ` Darren Hart
2012-06-01 21:47 ` Tom Zanussi [this message]
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=1338587240.28421.13.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=dvhart@linux.intel.com \
--cc=yocto-infrastructure@yoctoproject.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.