Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: stanshebs@earthlink.net
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use Doxygen for internals documentation
Date: Tue, 11 Feb 2014 19:19:00 -0000	[thread overview]
Message-ID: <201402111919.s1BJJfLP012816@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <52FA7509.4010400@earthlink.net> (message from Stan Shebs on Tue,	11 Feb 2014 11:07:53 -0800)

> Date: Tue, 11 Feb 2014 11:07:53 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> On 2/6/14 3:55 PM, Stan Shebs wrote:
> > Here is the official patch for the introduction of Doxygen that I
> > proposed last fall.
> 
> This is now pushed.
> 
> I've added http://sourceware.org/gdb/wiki/DoxygenForGDB as the
> initial info on what to do with it.
> 
> I've also got defs.h, minsyms.h, and utils.[hc] in various states
> of doxygenation, but won't spend a whole lot more time on them
> before pushing them.
> 
> For other popular header files, I suggest that if people
> want to jump on any, that we use the wiki page as a simple
> reservation system - although basic doxygenation of a file
> need take only a few minutes, one invariably sees many ways
> to fix up the comment blocks.

When did we agree that using doxygen was a good idea?

I don't want to spend my time on uglifying the source code with stuff
that will never result in usable documentation.

I don't want to be distracted by markup when I'm reading source code
or comments.

Most of all, I don't want to spend any time on arguing about these
stupid things.


  reply	other threads:[~2014-02-11 19:19 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
2014-02-11 19:08 ` Stan Shebs
2014-02-11 19:19   ` Mark Kettenis [this message]
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=201402111919.s1BJJfLP012816@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --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