From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: rationale for including checkouts in both layers and yocto git repos?
Date: Tue, 22 Jul 2014 09:28:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407220928300.4557@localhost> (raw)
In-Reply-To: <CAJTo0LYW2b9mE95EW+uK-H8E2ihtwmGNpk0U1Mz2PmzB_NX==g@mail.gmail.com>
On Tue, 22 Jul 2014, Burton, Ross wrote:
> On 22 July 2014 14:15, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > i just noticed that, across the two major repos for yocto:
> >
> > http://layers.openembedded.org/layerindex/branch/master/layers/
> > http://git.yoctoproject.org/
> >
> > there's a wee bit of duplication in that the second repo above
> > duplicates a lot of the meta- layers found in the first location. is
> > that deliberate? or can things be more properly placed in a single
> > location?
>
> The former - the layer index - is a curated index of every known
> layer. It doesn't contain any layers, and is merely a (searchable,
> human-readable, tagged) index.
>
> The later is the list of all git repositories on the official Yocto
> Project git server. It contains layers, kernel forks, applications
> and more.
>
> There is no duplication here.
ah, got it.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-07-22 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 13:15 rationale for including checkouts in both layers and yocto git repos? Robert P. J. Day
2014-07-22 13:27 ` Burton, Ross
2014-07-22 13:28 ` Robert P. J. Day [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=alpine.LFD.2.11.1407220928300.4557@localhost \
--to=rpjday@crashcourse.ca \
--cc=ross.burton@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.