Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Use Doxygen for internals documentation
Date: Sat, 08 Feb 2014 05:27:00 -0000	[thread overview]
Message-ID: <CADPb22TUsrBc69vZrCM21rk60vxYTrVos+ggnZXMCjhPxAA8Jw@mail.gmail.com> (raw)
In-Reply-To: <52F420E0.9050203@earthlink.net>

On Thu, Feb 6, 2014 at 3:55 PM, Stan Shebs <stanshebs@earthlink.net> wrote:
> Here is the official patch for the introduction of Doxygen that I
> proposed last fall.
>
> This differs from the RFC version in including a filter as
> suggested by Pedro, and having an index page that points to the
> different sets of pages.
>
> Among other things, the filter gives us the option of flagging
> Doxygen comments with "/* * ", which is lower-impact than the
> previous requirement of putting "/**" on a line by itself - in
> other words, just adding a " *" to existing comments.
>
> As before, "cd doc; make doxy" in an objdir creates, then browse
> doc/doxy/index.html to connect to everything.
>
> In the absence of any fatal flaws, I expect to commit this next
> week, and then follow up with patches that doxygenate some
> representative header files.  At some point we'll also want to
> add a snapshot-generated set of pages to the website.

Awesome!


  parent reply	other threads:[~2014-02-08  5:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 23:55 Stan Shebs
2014-02-07 13:29 ` Yao Qi
2014-02-07 15:36 ` Ludovic Courtès
2014-02-07 16:18   ` Eli Zaretskii
2014-02-08  9:59   ` Sergio Durigan Junior
2014-02-08 16:54     ` Ludovic Courtès
2014-02-08  5:27 ` Doug Evans [this message]
2014-02-11 19:08 ` Stan Shebs
2014-02-11 19:19   ` Mark Kettenis
2014-02-11 19:28     ` Eli Zaretskii
2014-02-11 19:52     ` Stan Shebs

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=CADPb22TUsrBc69vZrCM21rk60vxYTrVos+ggnZXMCjhPxAA8Jw@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@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