public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Laffey <joe@laffeycomputer.com>
To: gcc@gcc.gnu.org
Subject: Downloads
Date: Thu, 15 May 2003 17:35:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0305151232090.24978@alfred.laffeycomputer.com> (raw)

Hi,

I run the mirror mirrors.laffeycomputer.com. I notcie that a good number
of people are too ignorant to read the documentation first, and they
download ALL the files within the directory of a particular release.

I bet you could save yourself and the mirrors (and the users) some
bandwidth by placing all of the individual files that are included in the
main tarball (e.g. gcc-3.3.tar.gz) into a subfolder called something like
"separate_components". This way, most people would not download them along
with the full tarball.

Just a thought. Thanks for GCC!

--
Joe Laffey              |  Want to convert subnet masks between different
LAFFEY Computer Imaging |  notations, or figure the number of IPs in a block?
St. Louis, MO           |  Whatmask-It's FREE - www.laffeycomputer.com/wm.html
------------------------------------------------------------------------------

             reply	other threads:[~2003-05-15 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 17:35 Joe Laffey [this message]
2003-05-15 19:05 ` Downloads Gerald Pfeifer
2003-05-15 19:21   ` Downloads Joe Laffey
2003-05-15 22:22   ` Downloads Joseph S. Myers
2003-05-15 22:25     ` Downloads Joe Laffey
2003-05-16  8:38 Downloads Volker Reichelt
2003-05-16 10:09 ` Downloads Gerald Pfeifer
2003-05-16 10:20   ` Downloads Joseph S. Myers
2003-05-19 21:01     ` Downloads Karl Eichwalder
2003-05-19 21:04       ` Downloads Joseph S. Myers
2003-05-20 16:17         ` Downloads Karl Eichwalder
2003-05-20 18:24           ` Downloads Joseph S. Myers
2003-05-16 19:24   ` Downloads Mark Mitchell
2003-05-16 14:58 ` Downloads E. Weddington

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.LNX.4.53.0305151232090.24978@alfred.laffeycomputer.com \
    --to=joe@laffeycomputer.com \
    --cc=gcc@gcc.gnu.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).