From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix perl re-execution issues
Date: Mon, 16 Apr 2012 17:51:33 +0100 [thread overview]
Message-ID: <1469677.3CtmNycder@helios> (raw)
In-Reply-To: <cover.1334594354.git.paul.eggleton@linux.intel.com>
On Monday 16 April 2012 17:43:01 Paul Eggleton wrote:
> Fix re-execution issues within perl.
>
> Note: I identified that some references to /usr/include are still not
> being substituted before or after this patch - you can see these by
> doing "grep -rI '/usr/include' *"
er, that should be:
grep -rI "'/usr/include'" *
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-16 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 16:43 [PATCH 0/1] Fix perl re-execution issues Paul Eggleton
2012-04-16 16:43 ` [PATCH 1/1] perl: fix re-execution of patch/configure Paul Eggleton
2012-04-18 15:48 ` Enrico Scholz
2012-04-16 16:51 ` Paul Eggleton [this message]
2012-04-17 14:19 ` [PATCH 0/1] Fix perl re-execution issues Saul Wold
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=1469677.3CtmNycder@helios \
--to=paul.eggleton@linux.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