public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: Matthew Langford <langfml@Eng.Auburn.EDU>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, gcc@gnu.org
Subject: Re: http://gcc.gnu.org/mirrors.html
Date: Wed, 12 Dec 2001 16:54:00 -0000	[thread overview]
Message-ID: <20011212190100.A10665@disaster.jaj.com> (raw)
In-Reply-To: <Pine.SOL.4.10.10112071431440.16876-100000@caspian.eng.auburn.edu>; from langfml@Eng.Auburn.EDU on Fri, Dec 07, 2001 at 04:08:38PM -0600

Matthew Langford wrote:
> Gerald Pfeifer wrote:
> > We only list those mirror sites that inform us that they want to be
> > listed.
> 
> Do these sites have to mirror all the GCC pages or just the release
> directories?

Sites can mirror whatever subset of stuff they want to mirror.  It's their
diskspace, after all.


> You _know_ they are mirroring, and they are mirroring a
> gzipped release of your software.  Why not mention _them_ on your
> downloads page?

Maybe they don't want the entire world downloading from them.

People choose to mirror software for reasons /other/ than making it
available to everyone else out there.  I used to mirror a subset of the
Linux kernel patches repository, but it was for me and my colleagues
in the same building, not for the rest of the planet.  Listing me as a
"mirror site" would have been harmful, not helpful.


> You are making people come to you, like it's a special privilege to mirror
> GCC,

In a way it is:  known mirror sites are allowed to bypass some (all?) of
the connection limits on the FTP server.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2001-12-12 23:58 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     ` Phil Edwards [this message]
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           ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer
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=20011212190100.A10665@disaster.jaj.com \
    --to=pedwards@disaster.jaj.com \
    --cc=gcc@gnu.org \
    --cc=langfml@Eng.Auburn.EDU \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).