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 14:19:36 +0100 [thread overview]
Message-ID: <20140302141936.10852ded@skate> (raw)
In-Reply-To: <53131901.3030006@gmx.net>
Dear Peter K?mmel,
On Sun, 02 Mar 2014 12:41:53 +0100, Peter K?mmel wrote:
> >>> 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?
>
> http://patchwork.ozlabs.org/patch/320476/
> http://patchwork.ozlabs.org/patch/320475/
Thanks. Apparently you or someone else has already updated the status
of all the other patches.
> But I haven't tested them with current master, but I could check with master next week.
Yes, it would be good. Also, Fatih, could you have a look at Peter's
patches, and give your Acked-by/Reviewed-by as appropriate?
> BTW, what's the correct way to update a patch?
Resend it to the list, after updating it to the latest master. Make
sure you change the patch version by doing:
git send-email --subject-prefix="PATCH v2"
and by including a changelog either in the patch itself below the "---"
sign, or in the cover letter.
See
http://buildroot.org/downloads/manual/manual.html#_patch_revision_changelog
for more details.
> Just sending to the list like a new one and to superseded on patchwork?
Yes, but make sure to change the subject prefix to include a version
number, and include a changelog in the cover letter.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-02 13:19 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
2014-03-02 11:41 ` Peter Kümmel
2014-03-02 13:19 ` Thomas Petazzoni [this message]
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=20140302141936.10852ded@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.