From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: add_setshow_cmd_full
Date: Wed, 26 Jun 2002 11:46:00 -0000 [thread overview]
Message-ID: <2110-Wed26Jun2002214426+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <87lm91evky.fsf@fleche.redhat.com> (message from Tom Tromey on 26 Jun 2002 12:36:13 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Date: 26 Jun 2002 12:36:13 -0600
>
> Assuming Andrew approves my most recent patch in this area, what do
> you think of the appended documentation patch?
It's okay, please commit it with the source patches.
> In Java it is standard to extract special comments in the source and
> use those to construct API documentation. I know a long time ago gdb
> did this, but it was abandoned. Anyway, wouldn't it be simpler to
> keep the docs up to date with something like this in place?
I don't mind going back to keeping the docs with the sources.
prev parent reply other threads:[~2002-06-26 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 13:40 Tom Tromey
2002-06-25 19:35 ` Andrew Cagney
2002-06-25 22:12 ` Tom Tromey
2002-06-26 7:40 ` Andrew Cagney
2002-06-26 10:56 ` Tom Tromey
2002-06-26 12:54 ` Andrew Cagney
2002-06-25 22:05 ` Eli Zaretskii
2002-06-25 22:13 ` Tom Tromey
2002-06-26 11:23 ` Tom Tromey
2002-06-26 11:46 ` Eli Zaretskii [this message]
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=2110-Wed26Jun2002214426+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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