From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Merge gdbarch.sh and doc/gdbint.texinfo?
Date: Tue, 18 Feb 2003 21:39:00 -0000 [thread overview]
Message-ID: <3E52A93E.70805@redhat.com> (raw)
Hello,
(ok, silly idea of the day)
At present the architecture vector is documented in two places:
- doc/gdbinit.texinfo
- gdbarch.sh
What do people think of moveing gdbarch.sh's table of methods into
gdbinit.texinfo and have gdbarch.sh extract them from there?
It would, if nothing else, get rid of the `you need documentation'
problem :-)
As a kind of related side effect, what do people think of making the
architecture vector table an appendix. That way it doesn't clutter up
the core internals documentation.
Andrew
next reply other threads:[~2003-02-18 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:39 Andrew Cagney [this message]
2003-02-19 7:24 Zaretskii Eli
2003-02-19 13:01 ` Andrew Cagney
2003-02-19 14:26 Zaretskii Eli
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=3E52A93E.70805@redhat.com \
--to=ac131313@redhat.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