From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Fixed packaging warnings
Date: Fri, 23 Mar 2012 12:03:55 +0000 [thread overview]
Message-ID: <1332504235.9740.392.camel@ted> (raw)
In-Reply-To: <cover.1332474081.git.lianhao.lu@intel.com>
On Fri, 2012-03-23 at 12:31 +0800, Lianhao Lu wrote:
> This patch set fixed misc packaging warnings.
>
> The following changes since commit b92aaf764e6de94fb9fdee610e8f6643ccf74894:
> Richard Purdie (1):
> gst-plugins-bluetooth: Don't install headers, man pages or .pc files
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib llu/warningfix2
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/warningfix2
>
> Lianhao Lu (5):
> pseudo: package the var/pseudo directory.
> gdb-cross-canadian: not shipping libiberty.
> ncurses: ship clear/reset in package.
> nativesdk/misc: set PKGSUFFIX for correct variable name expansion.
> libgcc: corrected -nativesdk package namings.
Merged to master, thanks!
Richard
prev parent reply other threads:[~2012-03-23 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 4:31 [PATCH 0/5] Fixed packaging warnings Lianhao Lu
2012-03-23 4:31 ` [PATCH 1/5] pseudo: package the var/pseudo directory Lianhao Lu
2012-03-23 4:31 ` [PATCH 2/5] gdb-cross-canadian: not shipping libiberty Lianhao Lu
2012-03-23 4:31 ` [PATCH 3/5] ncurses: ship clear/reset in package Lianhao Lu
2012-03-23 4:31 ` [PATCH 4/5] nativesdk/misc: set PKGSUFFIX for correct variable name expansion Lianhao Lu
2012-03-23 4:31 ` [PATCH 5/5] libgcc: corrected -nativesdk package namings Lianhao Lu
2012-03-23 12:03 ` 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=1332504235.9740.392.camel@ted \
--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.