All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 02 Sep 2011 17:21:49 +0200	[thread overview]
Message-ID: <1314976910.3526.36.camel@mattotaupa> (raw)
In-Reply-To: <1314969543.5939.586.camel@rex>

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

Am Freitag, den 02.09.2011, 14:19 +0100 schrieb Richard Purdie:
> On Fri, 2011-09-02 at 10:05 -0300, Otavio Salvador wrote:
> > On Fri, Sep 2, 2011 at 08:25, Paul Menzel wrote:

> > > 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.

I interpret your answer that the merge is planned. What is the right
time then?

> Speaking as someone who has problems trying to figure out where
> patches are intended for

Also now you have to decide to what list to send them to. Now you just
add a prefix/tag as is done on oe-devel already to differentiate between
oe.dev and meta-oe.

> and who tracks whether they've been applied,

Well, the list is not a patch tracker. The patch queue is [1].

> I do find the split useful...

Hmm, could you please elaborate?


Thanks,

Paul


[1] http://patches.openembedded.org/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2011-09-02 15:26 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 [this message]
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

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=1314976910.3526.36.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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.