From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: cinly.ooi@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Perl: No reference conversion for Porting/Glossary
Date: Fri, 18 Aug 2017 10:51:37 +0100 [thread overview]
Message-ID: <1503049897.32591.5.camel@linuxfoundation.org> (raw)
In-Reply-To: <1502846306-32417-1-git-send-email-cinly.ooi@intel.com>
On Wed, 2017-08-16 at 09:18 +0800, cinly.ooi@intel.com wrote:
> From: Ooi Cinly <cinly.ooi@intel.com>
>
> do_configure() will no longer convert references to
> /usr/include into /path/to/recipes-sysroot/usr/include
> for the file "Porting/Glossary".
>
> [YOCTO #11243]
>
> Signed-off-by: Ooi Cinly <cinly.ooi@intel.com>
> ---
> meta/recipes-devtools/perl/perl_5.24.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've queued this, I just wanted to note that I had to tweak the
shortlog. Its not clear from reading the version above what the change
is doing. The recipe is perl, not Perl too. I changed it to:
"perl: Don't change /usr/include references in docs to sysroot paths"
Cheers,
Richard
prev parent reply other threads:[~2017-08-18 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 1:18 [PATCH] Perl: No reference conversion for Porting/Glossary cinly.ooi
2017-08-18 9:51 ` 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=1503049897.32591.5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=cinly.ooi@intel.com \
--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