From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] A couple more fixes for the libdir QA check
Date: Mon, 15 Jul 2013 19:17:42 +0100 [thread overview]
Message-ID: <cover.1373912179.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 43c28375f97161e618fa54349c65be2058c33c53:
distrodata.bbaclass: change in git and svn package reporting (2013-07-12 10:12:13 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/libdir2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/libdir2
Paul Eggleton (2):
classes/insane: fix regression in libdir QA regex
classes/insane: allow libdir QA check to be skipped using INSANE_SKIP
meta/classes/insane.bbclass | 40 +++++++++++++++++++++++++---------------
1 file changed, 25 insertions(+), 15 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-07-15 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 18:17 Paul Eggleton [this message]
2013-07-15 18:17 ` [PATCH 1/2] classes/insane: fix regression in libdir QA regex Paul Eggleton
2013-07-15 18:17 ` [PATCH 2/2] classes/insane: allow libdir QA check to be skipped using INSANE_SKIP Paul Eggleton
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.1373912179.git.paul.eggleton@linux.intel.com \
--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