From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Matthew Langford <langfml@eng.auburn.edu>,
Phil Edwards <pedwards@disaster.jaj.com>
Cc: gcc@gnu.org
Subject: Re: http://gcc.gnu.org/mirrors.html
Date: Thu, 13 Dec 2001 15:28:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.43.0112140008410.99865-100000@pulcherrima.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20011213143953.A14040@disaster.jaj.com>
On Fri, 7 Dec 2001, Matthew Langford wrote:
> And yet, as I mentioned, there must be a gazillion GNU mirror sites.
> You _know_ they are mirroring, and they are mirroring a gzipped release
> of your software.
I assume you missed the fact that
http://gcc.gnu.org/gcc-2.95/gcc-2.95.html
http://gcc.gnu.org/gcc-2.95/gcc-2.95.1.html
http://gcc.gnu.org/gcc-2.95/gcc-2.95.2.html
http://gcc.gnu.org/gcc-2.95/gcc-2.95.3.html
and
http://gcc.gnu.org/gcc-3.0/ has been
have been referring to the GNU mirror sites for years, right?
> Why not mention _them_ on your downloads page?
That's a good suggestion, and I will try to add this tomorrow. (Note,
though, that the GNU site only carries a subset of what's on gcc.gnu.org
and most of its mirrors, namely current GCC releases.)
> [...] the poor saps who walked to your ivory tower and volunteered their
> mirrors?
Please tone down. Phil is a volunteer, I am a volunteer, and most others
here are volunteers as well; no money, little honor, few thanks.
> The link to the actual gcc.org download is spelled out but not an active
> link. I suppose this is to strongly encourage people to use the mirrors.
Right.
On Thu, 13 Dec 2001, Phil Edwards wrote:
> Mostly it's nothing more than a lack of time on the part of the
> volunteers at either end. No hoarding, no ivory-tower syndrome, just
> lack of time.
Exactly!
> I'll ignore the rest of your flames and just explain this: gcc.gnu.org
> is extremely overloaded. For that reason anonymous FTP has been severely
> restricted (and I think it's been disallowed completely on some of the
> more popular projects). We're trying to move anonymous CVS access off
> onto another system also.
Yup, and that seems to work fine now; I already have a patch and will
update the corresponding GCC page tomorrow. (Again, Matthew, also this
has been handled by volunteers exclusively.)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2001-12-13 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 14:11 http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-07 7:04 ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer
2001-12-07 14:20 ` http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-12 16:54 ` http://gcc.gnu.org/mirrors.html Phil Edwards
2001-12-12 17:23 ` http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-13 11:41 ` http://gcc.gnu.org/mirrors.html Phil Edwards
2001-12-13 15:28 ` Gerald Pfeifer [this message]
2001-12-13 16:26 ` http://gcc.gnu.org/mirrors.html Phil Edwards
2001-12-13 16:59 ` http://gcc.gnu.org/mirrors.html Matthew Langford
-- strict thread matches above, loose matches on Subject: below --
2000-05-31 0:28 http://gcc.gnu.org/mirrors.html Joerg Faschingbauer
2000-05-31 11:30 ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer
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=Pine.BSF.4.43.0112140008410.99865-100000@pulcherrima.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gnu.org \
--cc=langfml@eng.auburn.edu \
--cc=pedwards@disaster.jaj.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).