Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] New commands, dump/restore memory<-->file
Date: Thu, 28 Mar 2002 01:24:00 -0000	[thread overview]
Message-ID: <2593-Thu28Mar2002112045+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3CA2762E.6030009@cygnus.com> (message from Andrew Cagney on Wed, 27 Mar 2002 20:47:26 -0500)

> Date: Wed, 27 Mar 2002 20:47:26 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> That is why I was suggesting an advanced features section to put things 
> like this in.

If there's unhappiness with the current structure of the manual (which
is indeed a bit too shallow), I can think about grouping the material
differently, to make it deeper and with less top-level chapters.

However, a single chapter named "Advanced Features" is hardly any help
in this direction, since its name doesn't say anything about what's
in it, and so cannot help in locating material.

> The main thing though is a good tutorial/example so 
> people know how to string the commands together to do something useful :-)

I agree wholeheartedly that having more tutorial-level information
would be great.  Perhaps we should at least consider requesting a
couple of non-trivial examples with each command whose documentation
is submitted for approval.


  reply	other threads:[~2002-03-28  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 17:57 Michael Snyder
2002-03-26 22:50 ` Eli Zaretskii
2002-03-27  8:29   ` Andrew Cagney
2002-03-27 13:31   ` Michael Snyder
2002-03-27 13:45     ` Andrew Cagney
2002-03-27 17:09       ` Michael Snyder
2002-03-27 17:49         ` Andrew Cagney
2002-03-28  1:24           ` Eli Zaretskii [this message]
2002-03-28  1:15     ` Eli Zaretskii
2002-03-28 17:24 ` Michael Snyder

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=2593-Thu28Mar2002112045+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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