From: Viktor Ostashevskyi <ostash@ostash.kiev.ua>
To: "Carlos O'Donell" <codonell@redhat.com>
Cc: libc-help@sourceware.org, Roland McGrath <roland@hack.frob.com>
Subject: Re: Old pre 2.0 glibc releases
Date: Wed, 29 Jan 2020 17:29:00 -0000 [thread overview]
Message-ID: <CAJ4BaJH03hTtNh-atSTVfMnwVUFrWP3RHonCJvPirdCD_Br7Tg@mail.gmail.com> (raw)
In-Reply-To: <98b3565b-4aec-ab76-6e88-47210dbc8b53@redhat.com>
Hello,
ср, 29 січ. 2020 о 18:21 Carlos O'Donell <codonell@redhat.com> пише:
> On 1/29/20 12:12 PM, Viktor Ostashevskyi wrote:
> > Hello,
> >
> > Is there a place where it is possible to get old pre 2.0 glibc releases
> or
> > snapshots?
> >
>
> I'm not aware of any other place to look other than:
> https://ftp.gnu.org/gnu/libc/
>
> I've included Roland on the TO: since he might be able to track this down.
>
> May I ask what you goal is in finding the old releases?
>
Software archaeology :) Trying to investigate how glibc was developed and
evolved in early days. Glibc CVS tree helps a lot, but looks that some
files are missing from for some reason till 1995, also some files were
renamed by changing RCS file name, some files were removed completely from
CVS, etc.
--
З повагою, Осташевський Віктор
prev parent reply other threads:[~2020-01-29 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 17:12 Viktor Ostashevskyi
2020-01-29 17:21 ` Carlos O'Donell
2020-01-29 17:29 ` Viktor Ostashevskyi [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=CAJ4BaJH03hTtNh-atSTVfMnwVUFrWP3RHonCJvPirdCD_Br7Tg@mail.gmail.com \
--to=ostash@ostash.kiev.ua \
--cc=codonell@redhat.com \
--cc=libc-help@sourceware.org \
--cc=roland@hack.frob.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).