From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] package/glibc: security bump to 2.27
Date: Tue, 6 Feb 2018 19:58:07 +0100 [thread overview]
Message-ID: <20180206195807.517b6dd6@windsurf> (raw)
In-Reply-To: <CANLo3JjKkTHaZUgTjQ2-Pq114K3EbAO7yr74u4U-Wa5NW7z+5w@mail.gmail.com>
Hello,
On Tue, 6 Feb 2018 19:43:07 +0100, Romain Naour wrote:
> > Any reason not to use upstream tarball now that we use an official release?
>
> > https://ftp.gnu.org/gnu/glibc/glibc-2.27.tar.xz
>
> We are expecting to follow the glibc 2.27 stable branch as soon as new
> commits are backported, so keep git things in place.
Fully agreed.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-06 18:58 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
2018-02-06 16:50 ` Baruch Siach
2018-02-06 18:43 ` Romain Naour
2018-02-06 18:58 ` 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=20180206195807.517b6dd6@windsurf \
--to=thomas.petazzoni@bootlin.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