From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/03] Perl path contamination fixes
Date: Mon, 26 Sep 2011 15:45:03 +0100 [thread overview]
Message-ID: <cover.1317048110.git.richard.purdie@linuxfoundation.org> (raw)
The following changes since commit ed2a606909b9490ac57a3ad3db7a15e83a8664f9:
neon: Add libproxy to DEPENDS to ensure determinstic builds (2011-09-25 15:54:55 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rpurdie/master2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rpurdie/master2
and fix perl path contamination issues from the build system.
Richard Purdie (3):
openssl: Ensure perl scripts reference the correct perl
util-linux: Ensure perl scripts reference the correct perl
mc: Ensure perl scripts reference the correct perl
next reply other threads:[~2011-09-26 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 14:45 Richard Purdie [this message]
2011-09-26 14:45 ` [PATCH 01/03] openssl: Ensure perl scripts reference the correct perl Richard Purdie
2011-09-26 14:45 ` [PATCH 02/03] util-linux: " Richard Purdie
2011-09-26 14:45 ` [PATCH 03/03] mc: " Richard Purdie
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=cover.1317048110.git.richard.purdie@linuxfoundation.org \
--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.