Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/2] [1.2] Fix distro checks in sanity.bbclass
Date: Wed, 18 Apr 2012 08:10:50 -0700	[thread overview]
Message-ID: <4F8ED97A.4070907@linux.intel.com> (raw)
In-Reply-To: <cover.1334742865.git.paul.eggleton@linux.intel.com>

On 04/18/2012 02:56 AM, Paul Eggleton wrote:
> After actually testing the distro sanity check on current distro
> versions on top of master, two issues were discovered; these
> trivial patches fix those issues.
>
>
> The following changes since commit 973351cf2e338f07c11395d494193e9c62857f2d:
>
>    libproxy: remove dependency on gconf when x11 not in DISTRO_FEATURES (2012-04-18 00:31:24 +0100)
>
> are available in the git repository at:
>    git://git.openembedded.org/openembedded-core-contrib paule/sanity-distro-fix
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/sanity-distro-fix
>
> Paul Eggleton (2):
>    classes/sanity: trim trailing newline when reading
>      /etc/redhat-release
>    classes/sanity: import regular expression module in SuSE distro check
>
>   meta/classes/sanity.bbclass |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-04-18 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  9:56 [PATCH 0/2] [1.2] Fix distro checks in sanity.bbclass Paul Eggleton
2012-04-18  9:56 ` [PATCH 1/2] classes/sanity: trim trailing newline when reading /etc/redhat-release Paul Eggleton
2012-04-18  9:56 ` [PATCH 2/2] classes/sanity: import regular expression module in SuSE distro check Paul Eggleton
2012-04-18 15:10 ` Saul Wold [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=4F8ED97A.4070907@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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