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] util-linux: fix packaging of readprofile
Date: Fri, 02 Sep 2011 18:18:22 +0100 [thread overview]
Message-ID: <1314983902.5939.621.camel@rex> (raw)
In-Reply-To: <572ada82123de7827679cc56e0a2dd8ae83abca3.1314915824.git.josh@linux.intel.com>
On Thu, 2011-09-01 at 15:25 -0700, Joshua Lock wrote:
> We rename readprofile to readprofile.util-linux so we need to use that binary
> name in the FILES entry for the readprofile package.
>
> Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> meta/recipes-core/util-linux/util-linux.inc | 2 +-
> meta/recipes-core/util-linux/util-linux_2.19.1.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-02 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1314915824.git.josh@linux.intel.com>
2011-09-01 22:25 ` [PATCH 1/1] util-linux: fix packaging of readprofile Joshua Lock
2011-09-02 17:18 ` 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=1314983902.5939.621.camel@rex \
--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