From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "Wold, Saul" <saul.wold@intel.com>
Subject: Re: [PATCH] dbus: fix paths in startup script, use useradd.bbclass for user creation
Date: Fri, 09 Sep 2011 18:43:51 +0100 [thread overview]
Message-ID: <1315590231.1986.8.camel@ted> (raw)
In-Reply-To: <1315557976.2519.88.camel@phil-desktop>
On Fri, 2011-09-09 at 09:46 +0100, Phil Blundell wrote:
> On Thu, 2011-09-08 at 08:44 -0700, Scott Garman wrote:
> > In any case, please submit your patch and I will advocate for its
> > inclusion in our 1.1 release.
>
> As requested.
[The shadow patch] merged to master, thanks.
Cheers,
Richard
prev parent reply other threads:[~2011-09-09 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 20:28 [PATCH] dbus: fix paths in startup script, use useradd.bbclass for user creation Phil Blundell
2011-09-08 3:58 ` Saul Wold
2011-09-08 6:54 ` Phil Blundell
2011-09-08 15:44 ` Scott Garman
2011-09-09 8:46 ` Phil Blundell
2011-09-09 17:43 ` Richard Purdie [this message]
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=1315590231.1986.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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