From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] package/glibc: security bump to 2.27
Date: Tue, 06 Feb 2018 14:51:40 +0100 [thread overview]
Message-ID: <878tc6tedv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180206125202.gdrli7t2g2bp4d3n@tarshish> (Baruch Siach's message of "Tue, 6 Feb 2018 14:52:02 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi Yann,
> On Tue, Feb 06, 2018 at 01:45:36PM +0100, Yann E. MORIN wrote:
>> On 2018-02-06 13:41 +0100, Thomas Petazzoni spake thusly:
>> > commit: https://git.buildroot.net/buildroot/commit/?id=c032e6825ad96e6d4b69cecde2402c02a2a356b5
>> > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/next
>>
>> Subject says "security bump". Sorry, but this is not a security bump.
>> This is a normal bump that happens to have security fixes.
>>
>> Otherwise, almost any bump of almost any package is a security bump...
> When we know that a package bump fixes a known security issue we usually note
> that in the subject line. Look for 'security' in commit subjects. You will
> find that many (most?) are just version bumps.
Indeed, this is in line with the other commits. It is somewhat sad that
glibc does not separate security fixes from feature releases, but that's
how it is.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-06 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 12:41 [Buildroot] [git commit branch/next] package/glibc: security bump to 2.27 Thomas Petazzoni
2018-02-06 12:45 ` Yann E. MORIN
2018-02-06 12:52 ` Baruch Siach
2018-02-06 13:51 ` Peter Korsgaard [this message]
2018-02-06 16:50 ` Baruch Siach
2018-02-06 18:43 ` Romain Naour
2018-02-06 18:58 ` 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=878tc6tedv.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