From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: bump to 2.28
Date: Mon, 3 Apr 2017 22:32:13 +0200 [thread overview]
Message-ID: <20170403223213.7d5d3490@free-electrons.com> (raw)
In-Reply-To: <20170321005943.3400-1-Adamduskett@outlook.com>
Hello,
On Mon, 20 Mar 2017 20:59:43 -0400, Adam Duskett wrote:
> In addition, I also modified the patch line numbers to match the
> changes. I also ran this package with test-pkg to insure that
> it built properly.
Please stop using the "first person" in your commit logs. Also, this
commit log was not very useful because it didn't mention which patches
have been upstreamed and in which commit. So I've replaced your commit
log with the following:
binutils: bump to 2.28
- Patch 0100-elf32-arm-no-data-fix.patch is upstream as of commit
6342be709e8749d0a44c02e1876ddca360bfd52f, so it is removed.
- Patch 0130-tc-xtensa.c-fixup-xg_reverse_shift_count-typo.patch is
upstream as of commit 78fb7e37eb8bb08ae537d6c487996ff17c810332, so
it is removed.
- Patch
0900-Revert-part-Set-dynamic-tag-VMA-and-size-from-dynami.patch is
upstream as of commit c646b02fdcae5f37bd88f33a0c4683ef13ad5c82, so
it is removed.
- All other patches are kept, just refreshed to apply cleanly on the
new binutils version.
Also, your .hash file change added many useless empty lines, so I dropped them.
Applied after fixing those issues. I've also done a few other binutils
related changes in the process:
- Remove unused 2.24 binutils hash.
- Switch to binutils 2.27 as the default
- Remove support for binutils 2.25.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-03 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 0:59 [Buildroot] [PATCH] binutils: bump to 2.28 Adam Duskett
2017-04-03 20:32 ` Thomas Petazzoni [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=20170403223213.7d5d3490@free-electrons.com \
--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