From: craig@jcb-sc.com
To: law@cygnus.com
Cc: craig@jcb-sc.com
Subject: Re: 1.1.2 bug, news lists
Date: Tue, 09 Mar 1999 15:47:00 -0000 [thread overview]
Message-ID: <19990309234749.17043.qmail@deer> (raw)
In-Reply-To: < 20852.920850205@hurl.cygnus.com > (message from Jeffrey A Law onSun, 07 Mar 1999 16:43:25 -0700)
>If you want to put a reference in the g77 documentation to the bugs and news
>file use:
>
> http://egcs.cygnus.com/onlinedocs/g77_bugs.html
> http://egcs.cygnus.com/onlinedocs/g77_news.html
>
>And if you want to reference the manual as a whole:
> http://egcs.cygnus.com/onlinedocs/g77_toc.html
Jeff, I've finally looked at these. *Really* nice. Two things:
1. g77_bugs.html grabs the entire "Known Causes Of Trouble..."
section of the manual, which is pretty big. I think this is
good, at least theoretically, but...
2. Chasing a link, even to a node in the currently open page,
can sometimes cause the entire page to be re-read. (E.g.
this happens starting with g77_bugs.html and chasing "But-Bugs"
in the first menu. At least for me, using lynx.)
Not sure what to suggest, except *possibly*, for the near term,
a specific link to the "Actual Bugs" section, which derives from
news.texi, might be useful...e.g. g77_actualbugs.html, in its
own menu under g77_bugs.html, if possible.
I'm planning on adding links to these resources (g77_toc.html,
g77_bugs.html, and g77_news.html) to g77's documentation for egcs 1.2
*and*, unless you say otherwise, for egcs 1.1.2.
But I won't get to it before 11pm tonite at the earliest, and perhaps
not until tomorrow or Thursday. (This is going to be a busy week for me,
for reasons unrelated to egcs.)
tq vm, (burley)
WARNING: multiple messages have this Message-ID
From: craig@jcb-sc.com
To: law@cygnus.com
Cc: craig@jcb-sc.com
Subject: Re: 1.1.2 bug, news lists
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <19990309234749.17043.qmail@deer> (raw)
Message-ID: <19990331234600.s55z61035d0MxXssSHXh02Ke-PsHXGgOTuWprpvPIkM@z> (raw)
In-Reply-To: <20852.920850205@hurl.cygnus.com>
>If you want to put a reference in the g77 documentation to the bugs and news
>file use:
>
> http://egcs.cygnus.com/onlinedocs/g77_bugs.html
> http://egcs.cygnus.com/onlinedocs/g77_news.html
>
>And if you want to reference the manual as a whole:
> http://egcs.cygnus.com/onlinedocs/g77_toc.html
Jeff, I've finally looked at these. *Really* nice. Two things:
1. g77_bugs.html grabs the entire "Known Causes Of Trouble..."
section of the manual, which is pretty big. I think this is
good, at least theoretically, but...
2. Chasing a link, even to a node in the currently open page,
can sometimes cause the entire page to be re-read. (E.g.
this happens starting with g77_bugs.html and chasing "But-Bugs"
in the first menu. At least for me, using lynx.)
Not sure what to suggest, except *possibly*, for the near term,
a specific link to the "Actual Bugs" section, which derives from
news.texi, might be useful...e.g. g77_actualbugs.html, in its
own menu under g77_bugs.html, if possible.
I'm planning on adding links to these resources (g77_toc.html,
g77_bugs.html, and g77_news.html) to g77's documentation for egcs 1.2
*and*, unless you say otherwise, for egcs 1.1.2.
But I won't get to it before 11pm tonite at the earliest, and perhaps
not until tomorrow or Thursday. (This is going to be a busy week for me,
for reasons unrelated to egcs.)
tq vm, (burley)
next prev parent reply other threads:[~1999-03-09 15:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 10:49 craig
[not found] ` < 19990305184852.5825.qmail@deer >
1999-03-05 13:57 ` Jeffrey A Law
[not found] ` < 16583.920670994@hurl.cygnus.com >
1999-03-05 14:14 ` Joe Buck
[not found] ` < 199903052214.OAA14694@atrus.synopsys.com >
1999-03-05 14:32 ` Jeffrey A Law
[not found] ` < 16727.920673121@hurl.cygnus.com >
1999-03-05 20:54 ` craig
[not found] ` < 19990306044434.7143.qmail@deer >
1999-03-07 15:23 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-05 20:54 ` craig
[not found] ` < 19990306044124.7129.qmail@deer >
1999-03-07 15:43 ` Jeffrey A Law
[not found] ` < 20852.920850205@hurl.cygnus.com >
1999-03-09 15:47 ` craig [this message]
[not found] ` < 19990309234749.17043.qmail@deer >
1999-03-09 16:21 ` Jeffrey A Law
[not found] ` < 27168.921025252@hurl.cygnus.com >
1999-03-10 7:52 ` craig
[not found] ` < 19990310155223.19500.qmail@deer >
1999-03-10 10:52 ` Jeffrey A Law
[not found] ` < 29303.921091928@hurl.cygnus.com >
1999-03-11 8:01 ` craig
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Joe Buck
1999-03-05 20:54 ` craig
[not found] ` < 19990306044013.7118.qmail@deer >
1999-03-07 14:50 ` Jeffrey A Law
[not found] ` < 20736.920846995@hurl.cygnus.com >
1999-03-18 18:22 ` craig
[not found] ` < 19990319021904.14950.qmail@deer >
1999-03-19 23:45 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Jeffrey A Law
1999-03-09 14:26 ` Gerald Pfeifer
[not found] ` < Pine.BSF.4.10.9903092305050.42367-100000@alkaid.dbai.tuwien.ac.at >
1999-03-12 22:52 ` craig
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` craig
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=19990309234749.17043.qmail@deer \
--to=craig@jcb-sc.com \
--cc=law@cygnus.com \
/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).