All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 02 Sep 2011 23:49:10 +0200	[thread overview]
Message-ID: <1315000152.6109.14.camel@mattotaupa> (raw)
In-Reply-To: <j3ri5g$dal$1@dough.gmane.org>

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

Am Freitag, den 02.09.2011, 23:34 +0200 schrieb Koen Kooi:
> Op 02-09-11 21:29, Andreas Müller schreef:
> > On Friday, September 02, 2011 08:48:38 PM Phil Blundell wrote:
> >> On Fri, 2011-09-02 at 17:21 +0200, Paul Menzel wrote:
> >>> Am Freitag, den 02.09.2011, 14:19 +0100 schrieb Richard Purdie:
> >>>> I do find the split useful...
> >>> 
> >>> Hmm, could you please elaborate?
> >> 
> >> Not that I'm Richard, but I do find the split useful as well. 
> >> Personally I am much less interested in the traffic on the oe-devel
> >> list and I often ignore that one; I've been somewhat tempted to just 
> >> unsubscribe altogether since there doesn't appear to be all that much
> >> of value (to me) going on there.
> 
> > 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.


Thanks,

Paul

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

  reply	other threads:[~2011-09-02 21:54 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 [this message]
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=1315000152.6109.14.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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.