From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] sstate.bbclass: Make sure we don't have an empty fixmepath file
Date: Fri, 18 May 2012 15:32:25 +0100 [thread overview]
Message-ID: <1337351545.28145.10.camel@ted> (raw)
In-Reply-To: <9e0928b2bbffb04eb4888be4d937e3b432160269.1337286797.git.mark.hatle@windriver.com>
On Thu, 2012-05-17 at 15:34 -0500, Mark Hatle wrote:
> Jason Wessel noticed that a package without any fixmepath entries would
> generate a sed warning about no input files. This patch resolves that
> by ensuring that an empty fixmepath file never gets written into the
> sstate archive. Also we avoid a second message by only doing xargs if
> we got input.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
> meta/classes/sstate.bbclass | 17 ++++++++++++-----
> 1 files changed, 12 insertions(+), 5 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-05-18 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 20:34 [PATCH 0/1] Fix sed warning message in sstate Mark Hatle
2012-05-17 20:34 ` [PATCH 1/1] sstate.bbclass: Make sure we don't have an empty fixmepath file Mark Hatle
2012-05-18 14:32 ` 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=1337351545.28145.10.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 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.