public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Joel Sherrill <joel@rtems.org>, Jeffrey Law <law@redhat.com>,
	 Overseers mailing list <overseers@sourceware.org>
Subject: Re: Ancient Archives of ftp.sourceware.org?
Date: Thu, 7 May 2020 11:25:35 -0500	[thread overview]
Message-ID: <CAF9ehCV-=jvRpXioKCpCJO1Ydc-07S1jxyzVY6ZzGK1iAuLZnQ@mail.gmail.com> (raw)
In-Reply-To: <m3ftcb90tr.fsf@pepe.airs.com>

On Thu, May 7, 2020 at 11:17 AM Ian Lance Taylor <ian@airs.com> wrote:

> Jeff Law via Overseers <overseers@sourceware.org> writes:
>
> > On Thu, 2020-05-07 at 09:01 -0500, Joel Sherrill wrote:
> >>
> >> Wow! How was newlib distributed back in the dark pre-sourceware age?
> >> I know we used it before 97/98 and got it via ftp.
> > I don't remember.   I would expect official releases from the newlib
> project
> > would have been via ftp *somewhere*, but I don't know where.  It was a
> long time
> > ago.
>
> It was just ftp.cygnus.com, along with the binutils, etc.
>

I checked archive.org and cygnus.com was gone as we know it before
archive.org
got a snapshot. The oldest required Flash to even see what it was. :(

>
> I verified that from, well, an old copy of the RTEMS documentation.
>
>
> https://docs.rtems.org/releases/rtemsdocs-4.6.0/share/rtems/html/relnotes/relnotes00007.html


LOL.. I'm a bit embarrassed you found it in old RTEMS documentation.

I guess those old versions are gone forever. It was worth a try.

Thanks.

--joel


>
> Ian
>

  reply	other threads:[~2020-05-07 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 15:44 Joel Sherrill
2020-05-06 19:29 ` Jeff Law
2020-05-07 14:01   ` Joel Sherrill
2020-05-07 14:18     ` Jeff Law
2020-05-07 16:17       ` Ian Lance Taylor
2020-05-07 16:25         ` Joel Sherrill [this message]
2020-05-07 17:10       ` Angela Marie Thomas

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='CAF9ehCV-=jvRpXioKCpCJO1Ydc-07S1jxyzVY6ZzGK1iAuLZnQ@mail.gmail.com' \
    --to=joel@rtems.org \
    --cc=law@redhat.com \
    --cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).