From: Ben Elliston <bje@redhat.com>
To: "Clayton, Curt J." <Curt.Clayton@UNISYS.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Confusion
Date: Fri, 19 Jul 2002 13:18:00 -0000 [thread overview]
Message-ID: <15672.29689.345427.797343@tooth.toronto.redhat.com> (raw)
In-Reply-To: <5EEDE746BE430A4BA8B1AD846011811E31E995@us-fft-exch-1.frf.unisys.com>
>>>>> "Clayton," == Clayton, Curt J <Curt.Clayton@UNISYS.com> writes:
Clayton,> The GCC 2.95.3 Manual postscript link on
Clayton,> http://gcc.gnu.org/onlinedocs/ is not gzipped as the target extension
Clayton,> suggests. The target is a PostScript file. Just thought you may want to
Clayton,> know.
$ file gcc.ps.gz
gcc.ps.gz: gzip compressed data, deflated, last modified: Thu Jun 7 03:39:09 2001, max compression, os: Unix
I suspect your browser is decompressing the file for you.
Cheers, Ben
parent reply other threads:[~2002-07-19 20:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5EEDE746BE430A4BA8B1AD846011811E31E995@us-fft-exch-1.frf.unisys.com>]
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=15672.29689.345427.797343@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=Curt.Clayton@UNISYS.com \
--cc=gcc-help@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).