From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] glibc 2.16/19 for Gentoo Prefix on antique kernels
Date: Wed, 28 Feb 2018 11:57:37 +0100 [thread overview]
Message-ID: <9399023.4aE4nyEdi7@porto> (raw)
In-Reply-To: <20180228102036.6d13cd2d@symphony.aura-online.co.uk>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Am Mittwoch, 28. Februar 2018, 11:20:36 CET schrieb James Le Cuirot:
> On Wed, 28 Feb 2018 11:10:13 +0100
>
> "Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
> > another option would be to (try to) revive glibc-2.5, 2.12, and 2.17
> > instead.
> >
>
> You maybe won't get the full details of the changes but all the patches
> are here. This looks like a much better breakdown than you get with
> their kernel patches.
>
> https://git.centos.org/summary/rpms!glibc.git
2.5 and 2.12 aren't there, but for 2.17 it looks good, this seems to be the
complete patchset. We should be able to translate that into a gentoo branch.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-28 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 6:17 [gentoo-dev] glibc 2.16/19 for Gentoo Prefix on antique kernels Benda Xu
2018-02-25 9:10 ` Michał Górny
2018-02-25 9:25 ` Benda Xu
2018-02-25 9:43 ` Michał Górny
2018-02-25 10:31 ` Benda Xu
2018-02-26 19:26 ` Michał Górny
2018-03-03 13:51 ` Benda Xu
2018-03-03 14:39 ` Michał Górny
2018-03-03 15:04 ` Benda Xu
2018-03-04 20:31 ` Andreas K. Huettel
2018-02-26 17:22 ` William Hubbs
2018-02-26 17:33 ` Alec Warner
2018-03-03 13:38 ` Benda Xu
2018-02-26 18:36 ` Andreas K. Huettel
2018-03-03 22:33 ` Benda Xu
2018-02-28 10:10 ` Andreas K. Huettel
2018-02-28 10:20 ` James Le Cuirot
2018-02-28 10:57 ` Andreas K. Huettel [this message]
2018-02-28 21:10 ` Andreas K. Huettel
2018-03-03 14:36 ` Benda Xu
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=9399023.4aE4nyEdi7@porto \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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