All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] State of your Qt 5 patches
Date: Sun, 2 Mar 2014 12:31:00 +0100	[thread overview]
Message-ID: <20140302123100.1b966bcd@skate> (raw)
In-Reply-To: <5313095B.7070204@gmx.net>

Dear Peter K?mmel,

On Sun, 02 Mar 2014 11:35:07 +0100, Peter K?mmel wrote:

> > Could you have a look at the following patches, and let me know which
> > ones no longer makes sense (because you have sent a new version) and
> > which ones still make sense:
> >
> >   http://patchwork.ozlabs.org/patch/320476/
> >   http://patchwork.ozlabs.org/patch/320475/
> >   http://patchwork.ozlabs.org/patch/320472/
> >   http://patchwork.ozlabs.org/patch/320462/
> >   http://patchwork.ozlabs.org/patch/320407/
> >   http://patchwork.ozlabs.org/patch/317465/
> >   http://patchwork.ozlabs.org/patch/317462/
> >   http://patchwork.ozlabs.org/patch/317461/
> 
> Hi Thomas,
> 
> the patches where intended for 2014.02.

And why wouldn't they be usable now?

> Maybe we should simply drop them and wait for Qt 5.3, planned for 29th Apr 2014:
> http://qt-project.org/wiki/Qt-5.3-release

That doesn't seem like a good idea. April, 29th will be very close to
2014.05-rc1, and so it might be too late to get the changes in.

I would really like those Qt 5.2.1 changes to get it now. Can you tell
me which patches from the list above still make sense?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-03-02 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01 23:28 [Buildroot] State of your Qt 5 patches Thomas Petazzoni
2014-03-02 10:35 ` Peter Kümmel
2014-03-02 11:31   ` Thomas Petazzoni [this message]
2014-03-02 11:41     ` Peter Kümmel
2014-03-02 13:19       ` Thomas Petazzoni
2014-03-02 11:47     ` Peter Kümmel

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=20140302123100.1b966bcd@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.