All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	"poky@yoctoproject.org Project" <poky@yoctoproject.org>
Subject: Re: [poky] [PATCH 0/7] User/group creation at preinstall
Date: Tue, 31 May 2011 16:16:05 -0500	[thread overview]
Message-ID: <4DE55A95.2090302@windriver.com> (raw)
In-Reply-To: <BANLkTimmP7rDQidBOBbA8TqVtHKMF7Bhuw@mail.gmail.com>

On 5/31/11 2:57 PM, Otavio Salvador wrote:
> On Tue, May 31, 2011 at 19:51, Scott Garman <scott.a.garman@intel.com> wrote:
>> That said, I have no idea what criteria should be used to determine which
>> list to send things to, and I'm sure I'm not the only one. Is this
>> documented anywhere?
> 
> It seems to me that poky list ought to be not used anymore and patches
> to be send to oe-core as AFAIK Yocto will base on it. Am I missing
> anything?
> 
> This is really confusing. This is not just regarding mailing lists but
> also IRC channels :-/
> 

As I understand it, the intention is the Poky list is used for Poky specific
items or to discuss (from a Poky specific point of view) oe-core items.. I.e.
problems, issues, etc from the usage of oe-core within the Poky use.

The confusion currently comes from many of the oe-core items used to live in the
Poky domain, and no longer due.  Unfortunately this will take a bit of education
for folks who don't contribute daily so that they know which mailing list to use.

(In otherwords the Poky list still has it's place, but only for Poky specific
discussions.)

--Mark



WARNING: multiple messages have this Message-ID (diff)
From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: "poky@yoctoproject.org Project" <poky@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [OE-core] [PATCH 0/7] User/group creation at preinstall
Date: Tue, 31 May 2011 16:16:05 -0500	[thread overview]
Message-ID: <4DE55A95.2090302@windriver.com> (raw)
In-Reply-To: <BANLkTimmP7rDQidBOBbA8TqVtHKMF7Bhuw@mail.gmail.com>

On 5/31/11 2:57 PM, Otavio Salvador wrote:
> On Tue, May 31, 2011 at 19:51, Scott Garman <scott.a.garman@intel.com> wrote:
>> That said, I have no idea what criteria should be used to determine which
>> list to send things to, and I'm sure I'm not the only one. Is this
>> documented anywhere?
> 
> It seems to me that poky list ought to be not used anymore and patches
> to be send to oe-core as AFAIK Yocto will base on it. Am I missing
> anything?
> 
> This is really confusing. This is not just regarding mailing lists but
> also IRC channels :-/
> 

As I understand it, the intention is the Poky list is used for Poky specific
items or to discuss (from a Poky specific point of view) oe-core items.. I.e.
problems, issues, etc from the usage of oe-core within the Poky use.

The confusion currently comes from many of the oe-core items used to live in the
Poky domain, and no longer due.  Unfortunately this will take a bit of education
for folks who don't contribute daily so that they know which mailing list to use.

(In otherwords the Poky list still has it's place, but only for Poky specific
discussions.)

--Mark


  reply	other threads:[~2011-05-31 21:19 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 18:13 [PATCH 0/7] User/group creation at preinstall Scott Garman
2011-05-31 19:53 ` Scott Garman
2011-05-31 18:13 ` [PATCH 1/7] shadow: recipe and patch cleanup Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-06-01  9:47   ` Phil Blundell
2011-06-01 12:34     ` Martyn Welch
2011-06-01 13:42       ` Phil Blundell
2011-06-01 17:43     ` Scott Garman
2011-06-01 21:05       ` Mark Hatle
2011-06-02 11:19         ` Phil Blundell
2011-09-01 14:46   ` Phil Blundell
2011-09-01 16:41   ` Phil Blundell
2011-09-01 16:54     ` Mark Hatle
2011-09-01 16:58       ` Phil Blundell
2011-09-01 17:25         ` Mark Hatle
2011-09-01 19:44           ` Phil Blundell
2011-09-01 21:59             ` Richard Purdie
2011-09-02  0:02               ` Mark Hatle
2011-09-02  7:15               ` Phil Blundell
2011-09-02  9:50               ` Phil Blundell
2011-09-02 14:03                 ` Richard Purdie
2011-09-02 18:43                   ` Phil Blundell
2011-09-02 19:17                     ` Mark Hatle
2011-05-31 18:13 ` [PATCH 3/7] base-passwd: add -cross recipe with default login.defs Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 4/7] useradd.bbclass: new class for managing user/group permissions Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 5/7] useradd-example: example recipe for using inherit useradd Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 19:09   ` Mark Hatle
2011-05-31 18:13 ` [PATCH 6/7] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 7/7] package_rpm.bbclass: make RPM use on-disk permissions Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:45 ` [poky] [PATCH 0/7] User/group creation at preinstall Koen Kooi
2011-05-31 18:45   ` Koen Kooi
2011-05-31 19:06   ` [poky] " Saul Wold
2011-05-31 19:06     ` Saul Wold
2011-05-31 19:09     ` Mark Hatle
2011-05-31 19:51     ` [poky] " Scott Garman
2011-05-31 19:51       ` Scott Garman
2011-05-31 19:57       ` [poky] " Otavio Salvador
2011-05-31 21:16         ` Mark Hatle [this message]
2011-05-31 21:16           ` [OE-core] " Mark Hatle
2011-05-31 21:27           ` [poky] " Scott Garman
2011-05-31 21:51             ` Richard Purdie
2011-05-31 21:25       ` Richard Purdie
2011-05-31 21:25         ` [OE-core] " Richard Purdie

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=4DE55A95.2090302@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@yoctoproject.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.