From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Annotate doco re-org
Date: Thu, 20 Mar 2003 16:48:00 -0000 [thread overview]
Message-ID: <3E79F0E6.4010803@redhat.com> (raw)
I guess I get to re-vamp the annotate doco. I'd like to do it as follows:
- verbatim insert the existing contents of doc/annotate.texi into
gdb.texinfo, but _after_ the MI chapter.
- change the old doc/annotate.texi file into a standalone quick 'n'
nasty migrating to MI document. Would contain commentary explaining
problems with various annotate #2 features and what their equivalent is.
- rewrite the annotate chapter (now part of gdb.texinfo) to reflect
annotate level #3.
Thoughts?
Andrew
next reply other threads:[~2003-03-20 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 16:48 Andrew Cagney [this message]
2003-03-21 4:36 ` 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=3E79F0E6.4010803@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).