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 00:28:57 +0100 [thread overview]
Message-ID: <20140302002857.2a9f166d@skate> (raw)
Hello Peter,
You have quite a few Qt5 related patches waiting in patchwork. However,
since you haven't used any version number for your patches, it's not
necessarily obvious which patches are still current, and which version
is the latest them.
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/
Remember that you can manage your own patches on patchwork (to mark the
old versions as superseded) by creating a patchwork account.
Fatih, I've Cc'ed you in case you have a bit of time to look at these
patches, and maybe review/test them.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-03-01 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 23:28 Thomas Petazzoni [this message]
2014-03-02 10:35 ` [Buildroot] State of your Qt 5 patches 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
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=20140302002857.2a9f166d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox