From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] utils.bbclass: fix for create_wrapper
Date: Thu, 19 May 2011 15:18:42 +0100 [thread overview]
Message-ID: <1305814722.3424.530.camel@rex> (raw)
In-Reply-To: <cover.1305745000.git.sgw@linux.intel.com>
On Wed, 2011-05-18 at 11:57 -0700, Saul Wold wrote:
> From: Saul Wold <sgw@linux.intel.com>
>
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: sgw/patch
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgw/patch
>
> Thanks,
> Saul Wold <sgw@linux.intel.com>
> ---
>
>
> Saul Wold (1):
> utils.bbclass: modify create_wrapper to correctly follow symlinks
Merged to master.
Cheers,
Richard
prev parent reply other threads:[~2011-05-19 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 18:57 [PATCH 0/1] utils.bbclass: fix for create_wrapper Saul Wold
2011-05-18 18:57 ` [PATCH 1/1] utils.bbclass: modify create_wrapper to correctly follow symlinks Saul Wold
2011-05-19 11:57 ` Gary Thomas
2011-05-19 14: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=1305814722.3424.530.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