From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 22:25:40 +0100 [thread overview]
Message-ID: <1306877140.27470.378.camel@rex> (raw)
In-Reply-To: <4DE546AE.1090301@intel.com>
On Tue, 2011-05-31 at 12:51 -0700, Scott Garman wrote:
> On 05/31/2011 12:06 PM, Saul Wold wrote:
> > On 05/31/2011 11:45 AM, Koen Kooi wrote:
> >> Shouldn't patches like this be sent to the oe-core list? It wouldn't
> >> have saved me from the selinux bug in shadow, though :)
> >>
> > Scott,
> >
> > I would agree with Koen, this is a oe-core change, not a Poky only
> > change, please resend this request to the oe-core list.
>
> Sure, I'll resend it to oe-core.
>
> 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?
We're trying to make this simpler over time:
bitbake changes -> bitbake-devel
Any code in oe-core -> oe-core list
Anything in poky not in oe-core/bitbake -> poky list
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "poky@yoctoproject.org Project" <poky@yoctoproject.org>
Subject: Re: [OE-core] [PATCH 0/7] User/group creation at preinstall
Date: Tue, 31 May 2011 22:25:40 +0100 [thread overview]
Message-ID: <1306877140.27470.378.camel@rex> (raw)
In-Reply-To: <4DE546AE.1090301@intel.com>
On Tue, 2011-05-31 at 12:51 -0700, Scott Garman wrote:
> On 05/31/2011 12:06 PM, Saul Wold wrote:
> > On 05/31/2011 11:45 AM, Koen Kooi wrote:
> >> Shouldn't patches like this be sent to the oe-core list? It wouldn't
> >> have saved me from the selinux bug in shadow, though :)
> >>
> > Scott,
> >
> > I would agree with Koen, this is a oe-core change, not a Poky only
> > change, please resend this request to the oe-core list.
>
> Sure, I'll resend it to oe-core.
>
> 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?
We're trying to make this simpler over time:
bitbake changes -> bitbake-devel
Any code in oe-core -> oe-core list
Anything in poky not in oe-core/bitbake -> poky list
Cheers,
Richard
next prev parent reply other threads:[~2011-05-31 21:29 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
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 [this message]
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=1306877140.27470.378.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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.