openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
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] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 02 Sep 2011 17:47:06 +0100	[thread overview]
Message-ID: <1314982026.5939.607.camel@rex> (raw)
In-Reply-To: <CAP9ODKq2-xj2v1EN461+Lzon2oXCw4g+swE1T62teuxK9TzfvA@mail.gmail.com>

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.

You therefore need an OE-Core subscription or both with the latter
recommended. The benefit is the two lists give some kind of filtering of
the email topics.

Cheers,

Richard




  reply	other threads:[~2011-09-02 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1314962732.3526.32.camel@mattotaupa>
2011-09-02 13:05 ` [oe] Please merge lists openembedded-devel and openembedded-core again Otavio Salvador
2011-09-02 13:19   ` 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 [this message]
2011-09-02 17:35             ` Otavio Salvador
2011-09-02 17:45               ` Richard Purdie
     [not found]     ` <1314976910.3526.36.camel@mattotaupa>
2011-09-02 17:00       ` Richard Purdie
2011-09-02 17:38         ` Otavio Salvador
2011-09-02 18:48       ` Phil Blundell

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=1314982026.5939.607.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;
as well as URLs for NNTP newsgroup(s).