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 0/3] Qt4 cleanup
Date: Wed, 18 May 2011 14:32:21 +0100	[thread overview]
Message-ID: <1305725541.3424.317.camel@rex> (raw)
In-Reply-To: <cover.1305709034.git.paul.eggleton@linux.intel.com>

On Wed, 2011-05-18 at 10:08 +0100, Paul Eggleton wrote:
> From: Paul Eggleton <paul.eggleton@linux.intel.com>
> 
> Remove Qt 4.6.3 in favour of 4.7.3 (which should be binary compatible with
> 4.6.x), add Upstream-Status to remaining patches and re-enable some patches
> that were missed with the original upgrade to 4.7.x.
> 
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
>   Branch: paule/qt4-cleanup-core
>   Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qt4-cleanup-core
> 
> Thanks,
>     Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> 
> 
> Paul Eggleton (3):
>   qt4: remove Qt 4.6.3
>   qt4: add comments and Upstream-Status to all patches
>   qt4: re-enable two 4.6.x patches in 4.7.3

I think the previous questions on the mailing list provided enough time
for discussion of this so merged to master, thanks. 

Cheers,

Richard






      parent reply	other threads:[~2011-05-18 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  9:08 [PATCH 0/3] Qt4 cleanup Paul Eggleton
2011-05-18  9:08 ` [PATCH 1/3] qt4: remove Qt 4.6.3 Paul Eggleton
2011-05-18  9:08 ` [PATCH 2/3] qt4: add comments and Upstream-Status to all patches Paul Eggleton
2011-05-18  9:08 ` [PATCH 3/3] qt4: re-enable two 4.6.x patches in 4.7.3 Paul Eggleton
2011-05-18  9:31 ` [PATCH 0/3] Qt4 cleanup Koen Kooi
2011-05-18 13:32 ` 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=1305725541.3424.317.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