From: Rob Savoye <rob.savoye@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doxygenate gdbtypes.h
Date: Wed, 05 Mar 2014 01:17:00 -0000 [thread overview]
Message-ID: <53167B17.1070107@linaro.org> (raw)
In-Reply-To: <53162EA7.9090804@earthlink.net>
On 03/04/2014 12:51 PM, Stan Shebs wrote:
> In this context, it's important that the standard says "preferred", not
> "required". As we've been discussing since last August, writing
> internals documentation as a separate manual in Texinfo has not worked
> out for GDB. Fortunately, the general coding standards do allow
> projects to set their own additional practices, where such changes
> do not contradict any explicit requirements set down by the FSF.
My Gnash project (a high priority project of the FSF) has used Doxygen
(and Docbook) for many years, and it's never been an issue with the FSF
or RMS at all, so I don't see what the problem is.
- rob -
next prev parent reply other threads:[~2014-03-05 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 0:16 Stan Shebs
2014-03-04 0:39 ` Mark Kettenis
2014-03-04 1:18 ` Stan Shebs
2014-03-04 17:36 ` Ludovic Courtès
2014-03-04 18:18 ` Joel Brobecker
2014-03-04 19:03 ` Stan Shebs
2014-03-04 19:15 ` Eli Zaretskii
2014-03-04 19:51 ` Stan Shebs
2014-03-05 1:17 ` Rob Savoye [this message]
2014-03-13 2:38 ` 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=53167B17.1070107@linaro.org \
--to=rob.savoye@linaro.org \
--cc=gdb-patches@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