All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Please merge lists openembedded-devel and openembedded-core again.
Date: Sat, 03 Sep 2011 19:36:03 +0200	[thread overview]
Message-ID: <4E626583.3060302@vollmann.ch> (raw)
In-Reply-To: <1314982026.5939.607.camel@rex>

On 09/02/11 18:47, Richard Purdie wrote:
> On Fri, 2011-09-02 at 10:53 -0300, Otavio Salvador wrote:
>> On Fri, Sep 2, 2011 at 10:33, Koen Kooi<koen@dominion.thruhere.net>  wrote:
>>> That sounds like people should just subscribe to oe-core if they want to be aware of changes instead of merging the 2 lists.
>>
>> Many times changes are related to meta-oe and oe-core and we'd need to
>> cross-post and seems wrong.
>
> I don't think this is actually true and its reasonable to assume
> discussion on OE-Core is seen by everyone.
Currently, the list descriptions read:
"openembedded-devel@lists.openembedded.org
Purpose: General discussion & patch submission

openembedded-core@lists.openembedded.org
Purpose: Discussions and patches for OE-Core"

Given this description I see hardly any post to openembedded-core
that shouldn't go to openembedded-devel as well.
But cross-posts are bad.

I'm not against two separate lists, but it should be clear what
should go to which list.  If the separation line is such that
there are more than 10% cross posts, then the lists should be joined.

BTW, some seem to think that openembedded-devel is for OE-Classic,
while openembedded-core should be for the new system (i.e. includes
oe-core and meta-oe).
That might be a better separation line to avoid cross posts, but
if that's what people want, this should be clearly said.

Another separation line would be the old -devel and -users separation.

Personally I could live with clearly separated lists, but I think
that just merging everything into openembedded-devel would be the
approach that serves all best, as everybody has his own separation
line anyway.

   Detlef



  parent reply	other threads:[~2011-09-03 17:41 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 [this message]
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

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=4E626583.3060302@vollmann.ch \
    --to=dv@vollmann.ch \
    --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.