From: Jason Molenda <jason-swarelist@molenda.com>
To: overseers@sourceware.org
Subject: Re: /sourceware/www is full (/www/gcc/htdocs/onlinedocs?)
Date: Fri, 19 Mar 2004 02:06:00 -0000 [thread overview]
Message-ID: <20040318172210.A949@molenda.com> (raw)
In-Reply-To: <20040319011212.GA21032@redhat.com>; from cgf@redhat.com on Thu, Mar 18, 2004 at 08:12:13PM -0500
On Thu, Mar 18, 2004 at 08:12:13PM -0500, Christopher Faylor wrote:
> One thing I notice taking up space is in /www/gcc/htdocs/onlinedocs.
> There seems to be compressed and uncompressed versions of files in this
> directory. Is it necessary to have both?
With the old mod_gzip, the .gz version would be sent instead of
the .html version resulting in a huge bandwidth savings. When the
system was on a T1, it was definitely worth it. Now I gather
bandwidth isn't such a problem for sourceware so it's less compelling.
It would still be appreciated by those on the other ends of slow
net connections, of coruse.
(but then again, I think we dropped this module when we went to RH
RPM based apache server. In which case they are probably completely
unused.)
J
next prev parent reply other threads:[~2004-03-19 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m34qslbqje.fsf@gossamer.airs.com>
[not found] ` <20040318170101.A91608@molenda.com>
2004-03-19 1:31 ` /sourceware/www is full Christopher Faylor
2004-03-19 1:47 ` /sourceware/www is full (/www/gcc/htdocs/onlinedocs?) Christopher Faylor
2004-03-19 2:06 ` Jason Molenda [this message]
2004-03-19 2:07 ` Joseph S. Myers
2004-03-19 2:17 ` /sourceware/www is full Ian Lance Taylor
2004-03-19 7:50 ` Joseph S. Myers
2004-03-20 0:49 ` Ian Lance Taylor
2004-03-19 14:12 ` Christopher Faylor
2004-03-20 1:14 ` Jonathan Larmour
[not found] ` <20040318170150.A91803@molenda.com>
2004-03-20 1:09 ` Jason Molenda
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=20040318172210.A949@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sourceware.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).