From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 02 Sep 2011 14:19:03 +0100 [thread overview]
Message-ID: <1314969543.5939.586.camel@rex> (raw)
In-Reply-To: <CAP9ODKpMU3yr==7+qyBvTyW3ikoSXtZqurKwsCn3Nn_54E0k7Q@mail.gmail.com>
On Fri, 2011-09-02 at 10:05 -0300, Otavio Salvador wrote:
> On Fri, Sep 2, 2011 at 08:25, Paul Menzel
> <paulepanter@users.sourceforge.net> wrote:
> > Dear OE folks,
> >
> >
> > it would be great if we could join the lists oe-devel and oe-core again.
> > As far as I know the only reason the list oe-core was created was to
> > discuss the initial setup and the creation of oe-core. Now that it has
> > been setup I do not see any reason to have two separate lists.
> >
> > I suggest to abandon/archive openembedded-core and use
> > openembedded-devel.
>
> I fully support this merge.
I'm not so sure rushing into this is a great idea. Speaking as someone
who has problems trying to figure out where patches are intended for and
who tracks whether they've been applied, I do find the split useful...
Cheers,
Richard
next prev parent reply other threads:[~2011-09-02 13:24 UTC|newest]
Thread overview: 21+ 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 ` Otavio Salvador
2011-09-02 13:19 ` Richard Purdie [this message]
2011-09-02 13:23 ` [OE-core] " Otavio Salvador
2011-09-02 13:33 ` Koen Kooi
2011-09-02 13:53 ` Otavio Salvador
2011-09-02 16:47 ` Richard Purdie
2011-09-02 17:35 ` Otavio Salvador
2011-09-02 17:45 ` Richard Purdie
2011-09-03 17:36 ` Detlef Vollmann
2011-09-02 15:21 ` Paul Menzel
2011-09-02 17:00 ` Richard Purdie
2011-09-02 17:38 ` Otavio Salvador
2011-09-02 20:18 ` Paul Menzel
2011-09-02 20:51 ` Andreas Müller
2011-09-02 18:48 ` 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
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=1314969543.5939.586.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox