From: Zaretskii Eli <ezaretski@elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: RE: Merge gdbarch.sh and doc/gdbint.texinfo?
Date: Wed, 19 Feb 2003 14:26:00 -0000 [thread overview]
Message-ID: <4D19136444628A40840EFE8C5AE04147017A40@ELTIMAIL1.elta.co.il> (raw)
This message was scanned for viruses and other malicious code by PrivaWall.
This mail was sent from ELTA SYS LTD.
> From: Andrew Cagney [mailto:ac131313@redhat.com]
> Sent: Wednesday, February 19, 2003 3:06 PM
>
> > 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
Fine with me.
This message is processed by the PrivaWall Email Security Server.
next reply other threads:[~2003-02-19 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 14:26 Zaretskii Eli [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 7:24 Zaretskii Eli
2003-02-19 13:01 ` Andrew Cagney
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=4D19136444628A40840EFE8C5AE04147017A40@ELTIMAIL1.elta.co.il \
--to=ezaretski@elta.co.il \
--cc=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