Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] zypper: Fix build with gcc 4.7
Date: Wed, 28 Mar 2012 10:16:01 +0100	[thread overview]
Message-ID: <1332926161.28414.195.camel@ted> (raw)
In-Reply-To: <1332902465-14472-1-git-send-email-raj.khem@gmail.com>

On Tue, 2012-03-27 at 19:41 -0700, Khem Raj wrote:
> More details in patch header
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  .../recipes-extended/zypper/zypper/gcc-scope.patch |   20 ++++++++++++++++++++
>  meta/recipes-extended/zypper/zypper_git.bb         |    3 ++-
>  2 files changed, 22 insertions(+), 1 deletions(-)
>  create mode 100644 meta/recipes-extended/zypper/zypper/gcc-scope.patch

Merged to master, thanks.

Richard




      reply	other threads:[~2012-03-28  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  2:41 [PATCH] zypper: Fix build with gcc 4.7 Khem Raj
2012-03-28  9:16 ` 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=1332926161.28414.195.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox