Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: A new strategy for internals documentation
Date: Thu, 08 Aug 2013 23:03:00 -0000	[thread overview]
Message-ID: <520423A2.6010304@earthlink.net> (raw)
In-Reply-To: <8361vfu9t4.fsf@gnu.org>

I'm not sure what we're arguing at this point, so let me see if I can
summarize your views on specific actions:

1. Delete gdbint.texinfo.

We're all agreed on this, right?

2. Add pieces of the manual to the wiki.

You doubt the value of this.  Should we forbid people from adding wiki
pages?

3. Introduce an annotation/structured scheme in source code comments.

You're skeptical, but not opposed to this, right?

4. Use Doxygen.

Are you for or against, or indifferent?

(For me Doxygen gets the nod by elimination, if nothing else.  In the
rather lengthy

http://en.wikipedia.org/wiki/Comparison_of_documentation_generators

there are not a lot of options that are portable, GPL, etc.  LLVM's use
of Doxygen, http://llvm.org/doxygen/index.html , seems pretty useful.)

Stan
stan@codesourcery.com


  reply	other threads:[~2013-08-08 23:03 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 [this message]
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

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=520423A2.6010304@earthlink.net \
    --to=stanshebs@earthlink.net \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    /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