Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Please merge lists openembedded-devel and openembedded-core again.
Date: Sat, 3 Sep 2011 09:08:28 +0200	[thread overview]
Message-ID: <20110903070828.GL3634@jama.jama.net> (raw)
In-Reply-To: <1315000152.6109.14.camel@mattotaupa>

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

On Fri, Sep 02, 2011 at 11:49:10PM +0200, Paul Menzel wrote:
> 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.

I don't care if it's all in one list or N > 2 separate lists because
I'll be subscribed to all and filter will merge all those e-mails to one
folder anyways..

But I see your point that it's harder to decide to which list(s) someone
should send his question..

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2011-09-03  7:13 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   ` [OE-core] " Richard Purdie
2011-09-02 13:23     ` 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 [this message]
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=20110903070828.GL3634@jama.jama.net \
    --to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox