From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: bump 2.25.x series to 2.25.1
Date: Wed, 22 Jul 2015 11:50:24 -0300 [thread overview]
Message-ID: <55AFADB0.3060101@zacarias.com.ar> (raw)
In-Reply-To: <20150722164819.2b9474e8@free-electrons.com>
On 22/07/15 11:48, Thomas Petazzoni wrote:
> I know we haven't been doing this so far, but should we name the option
> 2_25_X like we do for gcc, and therefore avoid renaming the option for
> every minor release ? Or keep it named 2_25 even if the version is
> 2.25.1, I don't really care.
Same dilemma here, though i preferred to skip the rename in the bump.
I can send a follow up patch to do the renaming, it seems fit to match
gcc i suppose.
Regards.
next prev parent reply other threads:[~2015-07-22 14:50 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 [this message]
2015-07-22 14:55 ` Thomas Petazzoni
2015-07-22 14:56 ` Gustavo Zacarias
2015-07-22 15:22 ` Thomas Petazzoni
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=55AFADB0.3060101@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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