From: Andrew Cagney <ac131313@redhat.com>
To: Zaretskii Eli <ezaretski@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Merge gdbarch.sh and doc/gdbint.texinfo?
Date: Wed, 19 Feb 2003 13:01:00 -0000 [thread overview]
Message-ID: <3E53813A.8050401@redhat.com> (raw)
In-Reply-To: <4D19136444628A40840EFE8C5AE04147017A33@ELTIMAIL1.elta.co.il>
(yes I probably should have sent this to gdb@)
>> From: Andrew Cagney [mailto:ac131313@redhat.com]
>> Sent: Tuesday, February 18, 2003 11:45 PM
>>
>> What do people think of moving gdbarch.sh's table of methods into
>> gdbinit.texinfo and have gdbarch.sh extract them from there?
>
>
> I'm all for it.
There is an `obvious' follow on to this. The target, along with some
other vectors, could also be put into separate appendicies.
> 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.
What about this? My guess at what to do next is:
- move the arch vector to the appendix and make it a separate file
- change it to use that weird @defun texi thingie
- add in the missing methods
- finally start worrying about the doco
Andrew
next prev parent reply other threads:[~2003-02-19 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 7:24 Zaretskii Eli
2003-02-19 13:01 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 14:26 Zaretskii Eli
2003-02-18 21:39 Andrew Cagney
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=3E53813A.8050401@redhat.com \
--to=ac131313@redhat.com \
--cc=ezaretski@elta.co.il \
--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