Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] QA Warnings Cleanup
Date: Fri, 01 Jul 2011 23:29:28 +0100	[thread overview]
Message-ID: <1309559368.20015.565.camel@rex> (raw)
In-Reply-To: <cover.1309533254.git.richard.purdie@linuxfoundation.org>

On Fri, 2011-07-01 at 16:17 +0100, Richard Purdie wrote:
> The following changes since commit 40ecaf6a59ba61e72d29d7e677197ef37c998408:
> 
>   uclibc: Add default uClibc.machine files (2011-07-01 00:40:10 +0100)
> 
> are available in the git repository at:
>   git://git.openembedded.org/openembedded-core-contrib rpurdie/master
>   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rpurdie/master
> 
> and clean up a variety of different QA warning issues
> 
> Richard  Purdie (6):
>   cairo: Clean up packaging and fix warnings
>   kernel.bbclass: Ensure kernel/* internal sysroot working directory
>     don't get packaged
>   libpcre: Fix QA warnings
>   python: Ensure libpython.so ends up in the .dev package
>   beecrypt: Fix up packaging QA warnings
>   insane.bbclass: Start to rework this so specific checks can be easily
>     made warnings/errors

I've merged these to master since the work well with the other QA
cleanups we're merging.

The SOLIBS variable discussion can happen and be followed up on later.

Cheers,

Richard




      parent reply	other threads:[~2011-07-01 22:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 15:17 [PATCH 0/6] QA Warnings Cleanup Richard Purdie
2011-07-01 15:17 ` [PATCH 1/6] cairo: Clean up packaging and fix warnings Richard Purdie
2011-07-01 15:17 ` [PATCH 2/6] kernel.bbclass: Ensure kernel/* internal sysroot working directory don't get packaged Richard Purdie
2011-07-01 15:17 ` [PATCH 3/6] libpcre: Fix QA warnings Richard Purdie
2011-07-01 15:17 ` [PATCH 4/6] python: Ensure libpython.so ends up in the .dev package Richard Purdie
2011-07-01 15:17 ` [PATCH 5/6] beecrypt: Fix up packaging QA warnings Richard Purdie
2011-07-01 15:19   ` Phil Blundell
2011-07-01 22:12     ` Richard Purdie
2011-07-02  7:40       ` Koen Kooi
2011-07-05 10:20       ` Phil Blundell
2011-07-01 15:17 ` [PATCH 6/6] insane.bbclass: Start to rework this so specific checks can be easily made warnings/errors Richard Purdie
2011-07-01 22:29 ` 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=1309559368.20015.565.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