From: Joel Brobecker <brobecker@adacore.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doxygenate gdbtypes.h
Date: Tue, 04 Mar 2014 18:18:00 -0000 [thread overview]
Message-ID: <20140304181803.GE4893@adacore.com> (raw)
In-Reply-To: <8761ntoogy.fsf@gnu.org>
> Just because some GNU packages use Doxygen (or CMake, or...) doesnât
> mean itâs a good idea; and it remains a GCS violation.
>
> > Two extra characters per comment block is not a "lot of random
> > garbage" or "vandalism" - over-the-top statements like that are not
> > going to convince anybody of anything.
>
> GNU has a history of well-written documentation and well-commented code.
> The rationale is documented, and IMO still holds.
>
> As a GNU user and hacker, Iâve long appreciated GNUâs luxurious approach.
> In contrast, I view the approach that Doxygen, Javadoc & co. favor as an
> insult to the reader.
>
I don't know yet how much I like Stan's approach and Doxygen, but
I support him in his efforts. And I need to also say that I am tired
of comments like this one that simply denegate someone's effort without
providing alternatives. And, I mean, real work. Not just shoulda/coulda/
woulda. What Mark and yourself are saying might be true, but you chose
to just criticize without substance. So I invite Stan and others to
simply ignore this destructive type of criticism, and I invite you
to stop sending it in that form.
I know both of you have a rich history of contributing to various
GNU projects, or free software in general, and I am not attacking that.
But someone is trying to improve our documentation, and the only
suitable answers are, IMO, to either support him, and guide him
towards alternatives.
--
Joel
next prev parent reply other threads:[~2014-03-04 18:18 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 [this message]
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
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=20140304181803.GE4893@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.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