From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: A new strategy for internals documentation
Date: Thu, 08 Aug 2013 20:41:00 -0000 [thread overview]
Message-ID: <877gfv530y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5201781A.3000607@earthlink.net> (Stan Shebs's message of "Tue, 06 Aug 2013 15:26:34 -0700")
>>>>> "Stan" == Stan Shebs <stanshebs@earthlink.net> writes:
Stan> Although GDB has had an internals manual for many years, nobody has
Stan> been especially happy with it. It is perennially out of date,
Stan> sometimes majorly so, and it is quite incomplete. With the passage of
Stan> time, the whole idea of an internals manual has come to seem like a
Stan> throwback to the old days, when the prospective GDB hacker's
Stan> information had to come from either printed books, or tape archives
Stan> downloaded from an FTP site.
Stan> Various ideas for how to fix have been floating around, generally with
Stan> the goal of improving the manual somehow, but nothing has developed
Stan> into action.
Stan> I propose a two-pronged strategy, first migrating the internals manual
Stan> to the wiki, and then introducing Doxygen for source code
Stan> documentation.
It all sounds good to me. Please get started :-)
Tom
prev parent reply other threads:[~2013-08-08 20:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 22:26 Stan Shebs
2013-08-07 4:28 ` Eli Zaretskii
2013-08-07 19:58 ` Stan Shebs
2013-08-08 17:28 ` Eli Zaretskii
2013-08-08 21:08 ` Doug Evans
2013-08-08 21:56 ` Eli Zaretskii
2013-08-08 23:03 ` Stan Shebs
2013-08-09 8:08 ` John Gilmore
2013-08-09 9:53 ` Eli Zaretskii
2013-08-09 9:35 ` Eli Zaretskii
2013-08-09 23:04 ` Stan Shebs
2013-08-09 9:53 ` Mark Kettenis
2013-08-09 23:28 ` Stan Shebs
2013-08-08 23:04 ` Doug Evans
2013-08-09 9:13 ` Eli Zaretskii
2013-08-10 1:13 ` Yao Qi
2013-08-21 18:09 ` Steinar Bang
2013-08-21 20:02 ` Eli Zaretskii
2013-08-22 18:29 ` Steinar Bang
2013-08-08 3:45 ` Yao Qi
2013-08-08 17:31 ` Eli Zaretskii
2013-08-09 1:30 ` John Gilmore
2013-08-09 9:26 ` Eli Zaretskii
2013-08-09 18:16 ` Tom Tromey
2013-08-09 18:36 ` Eli Zaretskii
2013-08-09 22:31 ` Stan Shebs
2013-08-09 23:32 ` Matt Rice
2013-08-10 2:24 ` John Gilmore
2013-08-08 20:43 ` Tom Tromey
2013-08-08 20:57 ` Doug Evans
2013-08-08 20:41 ` Tom Tromey [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=877gfv530y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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