From: Eli Zaretskii <eliz@is.elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: msnyder@redhat.com, jimb@cygnus.com, fnf@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: RFA: "maint print type" should print all the flag bits
Date: Wed, 12 Dec 2001 00:29:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1011212102625.10023G-100000@is> (raw)
In-Reply-To: <20011211144333.B22746@nevyn.them.org>
On Tue, 11 Dec 2001, Daniel Jacobowitz wrote:
> The maint commands are only useful if you're wandering around in the
> internals.
I don't necessarily agree, but anyway, it doesn't really matter, IMHO.
What does matter is that someone who wants to find a description of a
command--any command--should know in what manual to look. Working
with more than a single manual at a time is not very convenient in
most Info readers.
Since the internals manual omits more than it describes, I expect
someone who messes with the internals to read the code more than the
manual. So having all the commands in one manual is more convenient
even for a GDB developer.
next prev parent reply other threads:[~2001-12-12 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 11:14 Fred Fish
2001-12-09 19:08 ` Jim Blandy
2001-12-10 1:03 ` Eli Zaretskii
2001-12-10 12:44 ` Jim Blandy
2001-12-11 0:18 ` Eli Zaretskii
[not found] ` <3C162900.288B@redhat.com>
2001-12-11 9:21 ` Eli Zaretskii
2001-12-11 10:59 ` Andrew Cagney
2001-12-11 11:44 ` Daniel Jacobowitz
2001-12-11 17:47 ` Andrew Cagney
2001-12-11 19:14 ` Daniel Jacobowitz
2001-12-12 0:29 ` Eli Zaretskii
2001-12-12 0:29 ` Eli Zaretskii [this message]
2001-12-11 10:55 ` Jim Blandy
2001-12-11 11:16 ` Stan Shebs
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.1011212102625.10023G-100000@is \
--to=eliz@is.elta.co.il \
--cc=drow@mvista.com \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=msnyder@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