From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: bump default to version 2.23
Date: Wed, 22 Jun 2016 17:27:47 +0200 [thread overview]
Message-ID: <877fdhw8ek.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <312f3b85fab01ed234da9ff79ac982d0@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 22 Jun 2016 12:18:48 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> On 2016-06-22 12:13, Thomas Petazzoni wrote:
>> Default to n-1 has been our tradition for gcc/binutils/glibc for ages.
>>
>>> We're using latest uclibc-ng if it's suitable/for example.
>>
>> Cause uclibc-ng doesn't evolve much beyond bug fixes at the moment, so
>> there's not really a good reason to not use the latest version.
>>
>> Thomas
> Hi.
> There are outstanding security bugs that haven't been patched in
> buildroot for 22/23 yet which are fixed in the upcoming 24 release,
> and 22 has fixes on top of 23 already.
> And these patches need rebasing between 22 and 23, so i'd rather keep
> moving forward with them than backward.
> By introducing 23 as stable sooner in the development cycle rather
> than later we can spot issues quicker while also avoiding unnecessary
> work in backporting security patches across a broader spectrum.
> Regards.
I don't have an issue as such with us more aggressively following glibc
development if we decide to do so, but this kind of information should
be included in the commit message.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-06-22 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 10:09 [Buildroot] [PATCH] glibc: bump default to version 2.23 Gustavo Zacarias
2016-06-22 14:53 ` Peter Korsgaard
2016-06-22 15:02 ` Gustavo Zacarias
2016-06-22 15:13 ` Thomas Petazzoni
2016-06-22 15:18 ` Gustavo Zacarias
2016-06-22 15:27 ` Peter Korsgaard [this message]
2016-06-22 20:38 ` Arnout Vandecappelle
2016-06-22 22:58 ` Gustavo Zacarias
2016-06-27 20:00 ` Peter Korsgaard
2016-06-27 19:27 ` Peter Korsgaard
2016-06-27 20:56 ` Arnout Vandecappelle
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=877fdhw8ek.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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