From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Qt5: update to 5.2.1
Date: Mon, 17 Feb 2014 18:08:54 +0100 [thread overview]
Message-ID: <53024226.3070108@mind.be> (raw)
In-Reply-To: <20140214152948.424fd251@skate>
On 14/02/14 15:29, Thomas Petazzoni wrote:
> Dear Peter K?mmel,
>
> On Fri, 14 Feb 2014 15:18:59 +0100, Peter K?mmel wrote:
>> Signed-off-by: Peter K?mmel <syntheticpp@gmx.net>
>> ---
>> package/qt5/qt5.mk | 2 +-
>> .../qt5base-0001-Fix-build-MIPS64-bigendian.patch | 51 -------
>> ...-detect-posix_fallocate-at-configure-time.patch | 167 ---------------------
>> ...kit-0002-Fix-QtWebKit-build-on-ARM-softfp.patch | 35 -----
>> 4 files changed, 1 insertion(+), 254 deletions(-)
>
> When bumping a package, if some patches are removed, please explain in
> the commit log why they are removed. In this case, it would be good to
> mention that they can all be removed because they have been merged
> upstream.
If at all possible, add the upstream commit hashes as well. Or in this
case, the Change-Id tags that are already there are sufficient since they
can be grepped for in the logs.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-17 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 14:18 [Buildroot] [PATCH 1/1] Qt5: update to 5.2.1 Peter Kümmel
2014-02-14 14:29 ` Thomas Petazzoni
2014-02-17 17:08 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-14 15:12 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=53024226.3070108@mind.be \
--to=arnout@mind.be \
--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.