public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Laffey <joe@laffeycomputer.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
	gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: Downloads
Date: Thu, 15 May 2003 22:25:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0305151723300.24978@alfred.laffeycomputer.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0305152320380.14207@kern.srcf.societies.cam.ac.uk>

On Thu, 15 May 2003, Joseph S. Myers wrote:

> On Thu, 15 May 2003, Gerald Pfeifer wrote:
>
> > This is an excellent suggestion, and unless there are strong objection,
> > I will move all components and diff files into new subdirectories called
> > "components" and "diffs", respectively, tomorrow morning.
>
> If you hide parts of the distribution, then for minor releases (e.g.
> 3.3.1) it would perhaps make sense to put the main tarball in a
> subdirectory with the main diffs at toplevel instead, to encourage people
> to use the diffs if they already have the previous release rather than
> downloading the whole new tarball, if the aim is to save bandwidth.
>

While it is true that this would save the most bandwidth I would guess
that more people prefer to just deal with the full tarball.

The goals was save the bandwidth wasted by downloading EVERYTHING, instead
of just the big tarball. But you do have a point... perhaps a README with
a pointer to directions for applying the diff or soemthing?? *shrug*

I am not trying to make more work for you, though! I was just an idea...

--
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 22:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 17:35 Downloads Joe Laffey
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     ` Joe Laffey [this message]
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.0305151723300.24978@alfred.laffeycomputer.com \
    --to=joe@laffeycomputer.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=mark@codesourcery.com \
    --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).