From: "Eli Zaretskii" <eliz@elta.co.il>
To: David Carlton <carlton@kealia.com>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add meaningful section titles to PROBLEMS
Date: Sat, 20 Mar 2004 15:29:00 -0000 [thread overview]
Message-ID: <1659-Sat20Mar2004172615+0200-eliz@elta.co.il> (raw)
In-Reply-To: <yf2ptb8vijv.fsf@hawaii.kealia.com> (message from David Carlton on Fri, 19 Mar 2004 09:43:48 -0800)
> From: David Carlton <carlton@kealia.com>
> Date: Fri, 19 Mar 2004 09:43:48 -0800
>
> > As for some of the others, I think they would be better served as
> > notes in the documentation (i.e., gdb.texinfo).
>
> That's a good point - if we want to make users aware of certain
> well-known bugs, then gdb.texinfo is a much more visible place than
> PROBLEMS.
I disagree: we should certainly NOT document our bugs in the manual.
> (Nobody will see PROBLEMS other than possibly the specific
> individual, if any, who is installing that version of GDB by hand.)
> GCC has a section of known bugs in its manual; we should follow suit.
Why not follow suit of Emacs (which does have PROBLEMS, but not a
section about known bugs in the manual).
Note that PROBLEMS might mention problems that are actually bugs in
other related software, not necessarily in GDB per se. Are we going
to document them in the manual as well? I don't think so.
next prev parent reply other threads:[~2004-03-20 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 16:16 Andrew Cagney
2004-03-19 17:13 ` David Carlton
2004-03-19 17:33 ` Andrew Cagney
2004-03-19 17:43 ` David Carlton
2004-03-19 19:59 ` Andrew Cagney
2004-03-20 15:22 ` Eli Zaretskii
2004-03-20 15:29 ` Eli Zaretskii [this message]
2004-03-20 15:34 ` Eli Zaretskii
2004-03-25 21:07 ` Andrew Cagney
2004-03-19 16:50 Michael Elizabeth Chastain
2004-03-19 17:22 ` Andrew Cagney
2004-03-19 17:45 Michael Elizabeth Chastain
2004-03-20 15:26 ` 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=1659-Sat20Mar2004172615+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.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