Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] Misc Fixes and upgrades
Date: Mon, 19 Mar 2012 09:33:40 -0700	[thread overview]
Message-ID: <4F675FE4.3010503@linux.intel.com> (raw)
In-Reply-To: <cover.1331924359.git.nitin.a.kamble@intel.com>

On 03/16/2012 12:00 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> The following changes since commit 0676db79755b49b660f34e1c00769327fc299c58:
>
>    tcl: Fix bad RPATH QA warning (2012-03-16 16:47:44 +0000)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib nitin/misc
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
>
> Nitin A Kamble (7):
>    automake: upgrade from 1.11.2 to 1.11.3
Not Merged

>    distro-tracking: update status of recipes
>    python: fix install when libdir is not "lib"
>    pciutils: fix a do_compile failure
>    python-pyrex: quite packaging warnings
>    python-pycurl: fix packaging warnings
>    git: fix packaging warnings
>
>   .../conf/distro/include/distro_tracking_fields.inc |   24 ++--
>   meta/recipes-bsp/pciutils/pciutils_3.1.9.bb        |    5 +
>   meta/recipes-devtools/automake/automake.inc        |    2 +-
>   ...utomake_1.11.2_fix_for_pkglibexec_SCRIPTS.patch |  118 --------------------
>   .../prefer-cpio-over-pax-for-ustar-archives.patch  |   30 +++--
>   .../automake/automake/python-libdir.patch          |   32 +++---
>   .../{automake_1.11.2.bb =>  automake_1.11.3.bb}     |    8 +-
>   meta/recipes-devtools/git/git.inc                  |    2 +
>   .../python/python-pycurl_7.19.0.bb                 |    4 +
>   meta/recipes-devtools/python/python-pyrex_0.9.9.bb |    4 +-
>   .../python/fix_for_using_different_libdir.patch    |   78 +++++++++++++
>   meta/recipes-devtools/python/python_2.7.2.bb       |    2 +
>   12 files changed, 143 insertions(+), 166 deletions(-)
>   delete mode 100644 meta/recipes-devtools/automake/automake/automake_1.11.2_fix_for_pkglibexec_SCRIPTS.patch
>   rename meta/recipes-devtools/automake/{automake_1.11.2.bb =>  automake_1.11.3.bb} (85%)
>   create mode 100644 meta/recipes-devtools/python/python/fix_for_using_different_libdir.patch
>

All but the automake update was merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-03-19 16:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 19:00 [PATCH 0/7] Misc Fixes and upgrades nitin.a.kamble
2012-03-16 19:00 ` [PATCH 1/7] automake: upgrade from 1.11.2 to 1.11.3 nitin.a.kamble
2012-03-16 19:00 ` [PATCH 2/7] distro-tracking: update status of recipes nitin.a.kamble
2012-03-16 19:00 ` [PATCH 3/7] python: fix install when libdir is not "lib" nitin.a.kamble
2012-03-16 19:00 ` [PATCH 4/7] pciutils: fix a do_compile failure nitin.a.kamble
2012-03-16 19:00 ` [PATCH 5/7] python-pyrex: quite packaging warnings nitin.a.kamble
2012-03-16 19:00 ` [PATCH 6/7] python-pycurl: fix " nitin.a.kamble
2012-03-16 23:49   ` Richard Purdie
2012-03-17  0:35     ` Kamble, Nitin A
2012-03-17  9:29       ` Richard Purdie
2012-03-16 19:00 ` [PATCH 7/7] git: " nitin.a.kamble
2012-03-17 10:16   ` Paul Menzel
2012-03-19 16:33 ` Saul Wold [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=4F675FE4.3010503@linux.intel.com \
    --to=sgw@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