From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Please merge lists openembedded-devel and openembedded-core again.
Date: Sat, 03 Sep 2011 09:30:28 +0200 [thread overview]
Message-ID: <4E61D794.9050602@eukrea.com> (raw)
In-Reply-To: <1315000152.6109.14.camel@mattotaupa>
Le 02/09/2011 23:49, Paul Menzel a écrit :
> Am Freitag, den 02.09.2011, 23:34 +0200 schrieb Koen Kooi:
>> Op 02-09-11 21:29, Andreas Müller schreef:
>>> I would even prefer having additional meta-oe list separated from
>>> oe-dev.
>>
>> If there's enough need for it, that can get arranged.
>
> Why should that be needed? Maybe proposals could be explained and backed up
> with arguments for a discussion.
>
having a list for legacy oe and a list for new oe seems reasonnable : that's
not the same thing and legacy oe development is no more active (and activity
on the mailing list doesn't really show that oe legacy is dead).
And when a user has understood were to find layers, how to work with all these
layers, where are the recipes he needs in all the layers' directory tree, what
is the logic (or its absence) to classify recipes, how to customize them to
its need, and how to find in all that mess what broke something which was
working before the last pull, I'm sure he has the knowledge to subscribe to
the list of the layers he is using in order to follow their development ;-)
Eric
prev parent reply other threads:[~2011-09-03 8:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 11:25 Please merge lists openembedded-devel and openembedded-core again Paul Menzel
2011-09-02 13:05 ` [oe] " Otavio Salvador
2011-09-02 13:05 ` Otavio Salvador
2011-09-02 13:19 ` [oe] " Richard Purdie
2011-09-02 13:19 ` [OE-core] " Richard Purdie
2011-09-02 13:23 ` [oe] " Otavio Salvador
2011-09-02 13:23 ` [OE-core] " Otavio Salvador
2011-09-02 13:33 ` [oe] " Koen Kooi
2011-09-02 13:33 ` [OE-core] " Koen Kooi
2011-09-02 13:53 ` [oe] " Otavio Salvador
2011-09-02 13:53 ` [OE-core] " Otavio Salvador
2011-09-02 16:47 ` [oe] " Richard Purdie
2011-09-02 16:47 ` [OE-core] " Richard Purdie
2011-09-02 17:35 ` [oe] " Otavio Salvador
2011-09-02 17:35 ` [OE-core] " Otavio Salvador
2011-09-02 17:45 ` [oe] " Richard Purdie
2011-09-02 17:45 ` [OE-core] " Richard Purdie
2011-09-03 17:36 ` Detlef Vollmann
2011-09-02 15:21 ` Paul Menzel
2011-09-02 17:00 ` [oe] " Richard Purdie
2011-09-02 17:00 ` [OE-core] " Richard Purdie
2011-09-02 17:38 ` [oe] " Otavio Salvador
2011-09-02 17:38 ` [OE-core] " Otavio Salvador
2011-09-02 20:18 ` Paul Menzel
2011-09-02 20:51 ` Andreas Müller
2011-09-02 18:48 ` [oe] " Phil Blundell
2011-09-02 18:48 ` [OE-core] " Phil Blundell
2011-09-02 19:29 ` Andreas Müller
2011-09-02 21:34 ` Koen Kooi
2011-09-02 21:49 ` Paul Menzel
2011-09-03 7:08 ` Martin Jansa
2011-09-03 7:30 ` Eric Bénard [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=4E61D794.9050602@eukrea.com \
--to=eric@eukrea.com \
--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.