From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gnu@toad.com, yao@codesourcery.com, stanshebs@earthlink.net,
gdb@sourceware.org
Subject: Re: A new strategy for internals documentation
Date: Fri, 09 Aug 2013 18:36:00 -0000 [thread overview]
Message-ID: <83r4e2r9uh.fsf@gnu.org> (raw)
In-Reply-To: <8761vevigb.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: John Gilmore <gnu@toad.com>, yao@codesourcery.com, stanshebs@earthlink.net,
> gdb@sourceware.org
> Date: Fri, 09 Aug 2013 12:15:48 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Eli> Once again, the main problem (and some will say it's not a problem at
> Eli> all) is that the majority of GDB developers don't see any need in this
> Eli> manual's existence, or in any documentation of the internals besides
> Eli> what's in the comments.
>
> I just don't think this is true.
That is my conclusion from the discussions on this matter. I can show
citations, if needed.
If I'm wrong, please tell what form do you want the documentation of
the GDB internals to have.
next prev parent reply other threads:[~2013-08-09 18:36 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 [this message]
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
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=83r4e2r9uh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=stanshebs@earthlink.net \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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