Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	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: Tue, 11 Dec 2001 19:14:00 -0000	[thread overview]
Message-ID: <20011211221319.B5098@nevyn.them.org> (raw)
In-Reply-To: <3C16B72E.7020300@cygnus.com>

On Tue, Dec 11, 2001 at 05:47:26PM -0800, Andrew Cagney wrote:
> >On Tue, Dec 11, 2001 at 07:20:06PM +0200, Eli Zaretskii wrote:
> >
> >>> Date: Tue, 11 Dec 2001 07:40:48 -0800
> >>> From: Michael Snyder <msnyder@redhat.com>
> >>> 
> >>> Perhaps there needs to be a developers manual?
> >
> >>
> >>That's a possibility.  However, the number of maint commands is quite
> >>small, and hardly warrants a separate manual.
> >>
> >>How about having an Appendix where all maint commands would be
> >>documented?
> >
> >
> >We have an internals manual, don't we?  The maint commands are only
> >useful if you're wandering around in the internals.  So why not say as
> >much in the user manual, and document them in the internals manual?
> 
> 
> I think the ``maint'' commands are like the ``remote protocol spec'' and 
> the MI interface.  While not for the average user, they do define 
> external user accessable interfaces to GDB.

In that case, I'd almost rather rename the Internals manual to a
Developers manual - for development involving, rather than using but
not necessarily directly on, GDB.

I don't consider that fit for the User's manual.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-12-12  3:14 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 [this message]
2001-12-12  0:29                 ` Eli Zaretskii
2001-12-12  0:29             ` Eli Zaretskii
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=20011211221319.B5098@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --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