From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: bump 2.25.x series to 2.25.1
Date: Wed, 22 Jul 2015 17:22:07 +0200 [thread overview]
Message-ID: <20150722172207.577e2c58@free-electrons.com> (raw)
In-Reply-To: <55AFAF10.3020100@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 22 Jul 2015 11:56:16 -0300, Gustavo Zacarias wrote:
> On 22/07/15 11:55, Thomas Petazzoni wrote:
>
> > Dear Gustavo Zacarias,
> >
> > On Wed, 22 Jul 2015 11:50:24 -0300, Gustavo Zacarias wrote:
> >
> >> Same dilemma here, though i preferred to skip the rename in the bump.
> >
> > Well, you did rename, but to 2_25_1.
>
> Ah yes, i meant a general rename 2_25_X and so on.
Right. Follow-up patch is good. However, we'll have to handle legacy
symbols in Config.in.legacy :-/
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-22 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:01 [Buildroot] [PATCH] binutils: bump 2.25.x series to 2.25.1 Gustavo Zacarias
2015-07-22 14:48 ` Thomas Petazzoni
2015-07-22 14:50 ` Gustavo Zacarias
2015-07-22 14:55 ` Thomas Petazzoni
2015-07-22 14:56 ` Gustavo Zacarias
2015-07-22 15:22 ` 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=20150722172207.577e2c58@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