From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 00/16] fixes related to gcc 4.6.0 & patch upstream-status fields
Date: Wed, 11 May 2011 17:15:56 +0100 [thread overview]
Message-ID: <1305130556.30391.394.camel@rex> (raw)
In-Reply-To: <cover.1305062026.git.nitin.a.kamble@intel.com>
On Tue, 2011-05-10 at 14:16 -0700, Nitin A Kamble wrote:
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: nitin/misc
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
> Khem Raj (1):
> gcc-4.6.0: Apply linaro patches
>
> Nitin A Kamble (15):
> mdadm: compilation fix for gcc 4.6.0
> pax: fix for compiling with gcc 4.6.0
> systemtap: fix for compilation with gcc 4.6.0
> kexec-tools: fix compiler errors with gcc 4.6.0
> libzypp: fix compilatoin with gcc 4.6.0
> libpcre: fix the Upstream-Status format
> tar: fix Upstream-Status format
> sat-solver: fix Upstream-Status format
> cpio: fix upstream-status format
> subversion: fix upstream-status format
> python-imaging: fix upstream-status format
> patch-2.5.9: fix upstream-status format
> patch-2.6.1: fix upstream-status format
> binutils: fix upstream status format
> gcc-4.5.1: fix upstream-status format
Merged to master but I squashed all the upstream-status patches into one
patch since I didn't see the need for as many commits all making the
same logical change.
Cheers,
Richard
prev parent reply other threads:[~2011-05-11 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 21:16 [PATCH 00/16] fixes related to gcc 4.6.0 & patch upstream-status fields Nitin A Kamble
2011-05-10 21:16 ` [PATCH 01/16] gcc-4.6.0: Apply linaro patches Nitin A Kamble
2011-05-10 21:16 ` [PATCH 02/16] mdadm: compilation fix for gcc 4.6.0 Nitin A Kamble
2011-05-10 21:16 ` [PATCH 03/16] pax: fix for compiling with " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 04/16] systemtap: fix for compilation " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 05/16] kexec-tools: fix compiler errors " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 08/16] tar: fix Upstream-Status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 06/16] libzypp: fix compilatoin with gcc 4.6.0 Nitin A Kamble
2011-05-10 21:16 ` [PATCH 07/16] libpcre: fix the Upstream-Status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 10/16] cpio: fix upstream-status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 11/16] subversion: " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 09/16] sat-solver: fix Upstream-Status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 14/16] patch-2.6.1: fix upstream-status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 12/16] python-imaging: " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 13/16] patch-2.5.9: " Nitin A Kamble
2011-05-10 21:16 ` [PATCH 15/16] binutils: fix upstream status format Nitin A Kamble
2011-05-10 21:16 ` [PATCH 16/16] gcc-4.5.1: fix upstream-status format Nitin A Kamble
2011-05-11 16:15 ` 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=1305130556.30391.394.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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