From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3 0/2] Bug fixes
Date: Wed, 13 Jun 2012 14:56:38 +0100 [thread overview]
Message-ID: <1339595798.8065.27.camel@ted> (raw)
In-Reply-To: <1339586425-702-1-git-send-email-laurentiu.palcu@intel.com>
On Wed, 2012-06-13 at 14:20 +0300, Laurentiu Palcu wrote:
> Version 3 - bump connman PR. Thanks Ross for reminding me! :)
>
> Version 2 adds comments in connman.inc and xserver-nodm-init.bb to inform
> that xuser's USERADD_PARAMs must be in sync, as suggested by Ross.
>
> This patchset contains two bug fixes for:
> - Yocto #2467
> - Yocto #1465
>
> Laurentiu Palcu (2):
> sanity.bbclass: warn the user if BBPATH contains wrong entries
> connman: make useradd parameters consistent with rootless X
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-06-13 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 11:20 [PATCH v3 0/2] Bug fixes Laurentiu Palcu
2012-06-13 11:20 ` [PATCH v3 1/2] sanity.bbclass: warn the user if BBPATH contains wrong entries Laurentiu Palcu
2012-06-13 11:20 ` [PATCH v3 2/2] connman: make useradd parameters consistent with rootless X Laurentiu Palcu
2012-06-13 11:27 ` Burton, Ross
2012-06-13 13:56 ` 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=1339595798.8065.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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