From: Matthew Langford <langfml@Eng.Auburn.EDU>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gnu.org
Subject: Re: http://gcc.gnu.org/mirrors.html
Date: Fri, 07 Dec 2001 14:20:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.10.10112071431440.16876-100000@caspian.eng.auburn.edu> (raw)
In-Reply-To: <Pine.BSF.4.43.0112071430010.28109-100000@naos.dbai.tuwien.ac.at>
On Fri, 7 Dec 2001, Gerald Pfeifer wrote:
> On Thu, 6 Dec 2001, Matthew Langford wrote:
> > What's up with this page?
>
> I'm not a native speaker, but which part of "Please let us know if you
> are mirroring the GCC pages so we can note it here!" was unclear to you?
>
> 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? If all, why? It seems to me you have a problem getting
people to mirror GCC. 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. Why not mention _them_ on your
downloads page? It's all about _downloads_ and not total site mirroring.
As long you make sure the GNU site is kept semi-constantly up to date, a
mirror of GNU is a mirror of you.
You are making people come to you, like it's a special privilege to mirror
GCC, instead of looking to list already available mirrors, so people can
get your software and make things happen.
> (I'll happily apply a patch of yours to improve the wording on that
> page. Really!)
Okay, pseudo-patch: stick in a link to http://www.gnu.org/order/ftp.html,
saying these sites may be slightly slower to update, but are preferrable
to a trans-oceanic link. And then set cron jobs to make sure the GNU ftp
sites are mirroring at least the latest stable release.
--
MattLangford
next prev parent reply other threads:[~2001-12-07 22:09 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 ` Matthew Langford [this message]
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 ` 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=Pine.SOL.4.10.10112071431440.16876-100000@caspian.eng.auburn.edu \
--to=langfml@eng.auburn.edu \
--cc=gcc@gnu.org \
--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).