From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: OE TSC Minutes 4 June 2013
Date: Sat, 8 Jun 2013 00:20:52 +0200 [thread overview]
Message-ID: <20130607222052.GN22710@jama> (raw)
In-Reply-To: <CA+YB3rZ+pWVzy6_=PAa9QRTdsu+Y5OEGwdW7sLpLphnWZ-89yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
> a. oe-classic recipe migration status
> drop from agenda after this
Not sure why I got this idea now when it's "over" but would it be
possible to populate new layerindex with at least recipe names from
OE-classic?
I guess it would be hard to parse it completely as proper layer,
but it would be nice to search for "foo" and see that it's available in
OE-classic ready to be migrated to some layer - otherwise people will
just start from scratch which isn't always best way.
Even just names from migration wiki page would be enough to give people
heads-up that something similar is in OE-classic.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] OE TSC Minutes 4 June 2013
Date: Sat, 8 Jun 2013 00:20:52 +0200 [thread overview]
Message-ID: <20130607222052.GN22710@jama> (raw)
In-Reply-To: <CA+YB3rZ+pWVzy6_=PAa9QRTdsu+Y5OEGwdW7sLpLphnWZ-89yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
> a. oe-classic recipe migration status
> drop from agenda after this
Not sure why I got this idea now when it's "over" but would it be
possible to populate new layerindex with at least recipe names from
OE-classic?
I guess it would be hard to parse it completely as proper layer,
but it would be nice to search for "foo" and see that it's available in
OE-classic ready to be migrated to some layer - otherwise people will
just start from scratch which isn't always best way.
Even just names from migration wiki page would be enough to give people
heads-up that something similar is in OE-classic.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-06-07 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 21:54 OE TSC Minutes 4 June 2013 Jeff Osier-Mixon
2013-06-07 22:20 ` Martin Jansa [this message]
2013-06-07 22:20 ` [OE-core] " Martin Jansa
2013-06-07 22:30 ` Jeff Osier-Mixon
2013-06-07 22:30 ` [OE-core] " Jeff Osier-Mixon
2013-06-08 11:43 ` Paul Eggleton
2013-06-08 11:43 ` [OE-core] " Paul Eggleton
2013-06-07 22:50 ` Philip Balister
2013-06-07 22:50 ` [OE-core] " Philip Balister
2013-06-07 22:59 ` Jeff Osier-Mixon
2013-06-07 22:59 ` [OE-core] " Jeff Osier-Mixon
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=20130607222052.GN22710@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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.