From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [poky] [PATCH 0/7] User/group creation at preinstall
Date: Tue, 31 May 2011 14:27:55 -0700 [thread overview]
Message-ID: <4DE55D5B.6070307@intel.com> (raw)
In-Reply-To: <4DE55A95.2090302@windriver.com>
On 05/31/2011 02:16 PM, Mark Hatle wrote:
> 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.)
So presumably this would mean: if it's about a recipe that is not in
OE-core, it's Poky-specific?
Which would also mean that discussion about anything in the bitbake
classes belongs on OE-core as well, yes?
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-05-31 21:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:53 [PATCH 0/7] User/group creation at preinstall Scott Garman
2011-05-31 18:45 ` [poky] " Koen Kooi
2011-05-31 19:06 ` Saul Wold
2011-05-31 19:51 ` Scott Garman
2011-05-31 19:57 ` Otavio Salvador
2011-05-31 21:16 ` Mark Hatle
2011-05-31 21:27 ` Scott Garman [this message]
2011-05-31 21:51 ` Richard Purdie
2011-05-31 21:25 ` Richard Purdie
2011-05-31 19:53 ` [PATCH 1/7] shadow: recipe and patch cleanup Scott Garman
2011-05-31 19:53 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities 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 19:53 ` [PATCH 3/7] base-passwd: add -cross recipe with default login.defs Scott Garman
2011-05-31 19:53 ` [PATCH 4/7] useradd.bbclass: new class for managing user/group permissions Scott Garman
2011-05-31 19:53 ` [PATCH 5/7] useradd-example: example recipe for using inherit useradd Scott Garman
2011-05-31 19:53 ` [PATCH 6/7] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Scott Garman
2011-05-31 19:53 ` [PATCH 7/7] package_rpm.bbclass: make RPM use on-disk permissions Scott Garman
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=4DE55D5B.6070307@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@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