From: Michael Eager <eager@eagercon.com>
To: phil@ipal.net
Cc: gcc@gnu.org
Subject: Re: downloading GCC documentation
Date: Sat, 10 May 2003 16:44:00 -0000 [thread overview]
Message-ID: <3EBD2C76.7040109@eagercon.com> (raw)
In-Reply-To: <20030508205616.GA1298@aludra>
Speaking of documentation, is the source file for gccint.ps available
somewhere? I couldn't find it, and the ps file prints all of the page
numbers off the top of the page.
phil@ipal.net wrote:
> It would be nice if there was a link to allowing downloading the full
> GCC documentation tree as a tar.gz file. I have looked on the following
> pages and do not see such a link:
>
> http://gcc.gnu.org/
> http://gcc.gnu.org/faq.html
> http://gcc.gnu.org/onlinedocs/
> http://gcc.gnu.org/onlinedocs/gcc/
> http://gcc.gnu.org/onlinedocs/gcc-3.2.2/ (forbidden, but hey, I tried)
> http://gcc.gnu.org/onlinedocs/gcc-3.2.2/gcc/
> http://gcc.gnu.org/readings.html
>
> I want to read the documentation while "offline" (literally, while my
> slow dialup modem is busy downloading the latest of everything, which is
> usually the case 95% of the time) in my web browser. Alternatively,
> "one big HTML file" could work, although I suspect that would be
> unwieldy for something the scale of GCC. But I think the tar.gz thing
> should be readily doable.
>
> This would save me having to run wget recursively on the documentation,
> and rerunning it to be sure a file here or there didn't get missed
> (generally I figure two passes w/o any change in the downloaded tree
> means likely success). But with a tar.gz file, one download and an MD5
> check should do it.
>
> Further, the web server on gcc.gnu.org does not give a Last-modified
> header, so wget always retrieves each file all over again on each pass.
>
> I check the FTP server on the same hostname. The "pub" area does not
> seem to have the online docs files (even a recursive download would be
> better here as the timestamps would be preserved and be usable to avoid
> redundant downloading). The "www" area of the FTP server is not the
> gcc.gnu.org site; it appears to be empty.
>
> I am not subscribed to the mailing list. This is a suggestion for the
> web site since I have already downloaded the documentation (the hard
> way). However, if you have any communications for me about this, feel
> free to contact me by email.
>
--
Michael Eager Eager Consulting eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2003-05-10 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 20:57 phil
2003-05-08 21:07 ` Matthieu Moy
2003-05-10 16:44 ` Michael Eager [this message]
2003-05-10 19:02 ` Daniel Jacobowitz
2003-05-24 11:21 ` Gerald Pfeifer
2003-05-27 15:53 ` E. Weddington
2003-05-27 19:22 ` 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=3EBD2C76.7040109@eagercon.com \
--to=eager@eagercon.com \
--cc=gcc@gnu.org \
--cc=phil@ipal.net \
/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).