Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doxygenate gdbtypes.h
Date: Tue, 04 Mar 2014 19:15:00 -0000	[thread overview]
Message-ID: <83txbdrd10.fsf@gnu.org> (raw)
In-Reply-To: <53162394.3030604@earthlink.net>

> Date: Tue, 04 Mar 2014 11:03:48 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> > Just because some GNU packages use Doxygen (or CMake, or...) doesn’t
> > mean it’s a good idea; and it remains a GCS violation.
> 
> Paragraph and sentence, please?

From the "GNU Manuals" node:

   The preferred document format for the GNU system is the Texinfo
   formatting language.  Every GNU package should (ideally) have
   documentation in Texinfo both for reference and for learners.  Texinfo
   makes it possible to produce a good quality formatted book, using TeX,
   and to generate an Info file.  It is also possible to generate HTML
   output from Texinfo source.  See the Texinfo manual, either the
   hardcopy, or the on-line version available through `info' or the Emacs
   Info subsystem (`C-h i').

      Nowadays some other formats such as Docbook and Sgmltexi can be
   converted automatically into Texinfo.  It is ok to produce the Texinfo
   documentation by conversion this way, as long as it gives good results.


  reply	other threads:[~2014-03-04 19:15 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 [this message]
2014-03-04 19:51           ` Stan Shebs
2014-03-05  1:17             ` Rob Savoye
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=83txbdrd10.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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