From: Eli Zaretskii <eliz@is.elta.co.il>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@math.stanford.edu, drow@mvista.com,
gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] correct info about best C++ compilers/debug formats
Date: Tue, 04 Feb 2003 06:16:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1030204080907.22830F-100000@is> (raw)
In-Reply-To: <200302032121.h13LL2R32056@duracef.shout.net>
On Mon, 3 Feb 2003, Michael Elizabeth Chastain wrote:
> I tested it, too: I built gdb and 'makeinfo' worked fine.
As long as we are testing, perhaps someone could find a moment and TeX
the manual, to see that the additions typeset well.
Also, did you try to follow the external references, like this one:
See @ref{Debugging Options,,Options
for Debugging Your Program or @sc{gnu} CC, gcc.info, Using @sc{gnu} CC},
for more information.
In my experience, references to other manuals tend to confuse people, and
thus have a somewhat higher probability of being written incorrectly. I
cannot say I see anything wrong with this one, but I don't pretend to
remember the order of the arguments by heart ;-)
next prev parent reply other threads:[~2003-02-04 6:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 21:21 Michael Elizabeth Chastain
2003-02-04 6:16 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 14:41 Michael Elizabeth Chastain
2003-02-04 6:24 Michael Elizabeth Chastain
2003-02-04 8:08 ` Eli Zaretskii
[not found] <200302032008.h13K8M230404@duracef.shout.net>
2003-02-03 20:14 ` David Carlton
2003-02-04 6:08 ` Eli Zaretskii
2003-02-04 7:04 ` Andrew Cagney
2003-02-04 21:17 ` David Carlton
2003-02-05 5:54 ` Eli Zaretskii
2003-02-03 19:29 David Carlton
2003-02-03 18:27 David Carlton
2003-02-03 18:37 ` Daniel Jacobowitz
2003-02-03 19:23 ` Eli Zaretskii
2003-02-03 20:09 ` David Carlton
2003-02-03 20:49 ` Andrew Cagney
2003-02-04 6:14 ` Eli Zaretskii
2003-02-04 5:59 ` Eli Zaretskii
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.SUN.3.91.1030204080907.22830F-100000@is \
--to=eliz@is.elta.co.il \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.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