From: dewar@gnat.com (Robert Dewar)
To: aph@redhat.com, fjh@cs.mu.OZ.AU
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: "obvious" requirements
Date: Tue, 20 May 2003 22:58:00 -0000 [thread overview]
Message-ID: <20030520220843.556EFF2DA0@nile.gnat.com> (raw)
> Regardless of the academic history of this particular usage of the term,
> it nevertheless has a strongly vulgar connotation, and IMHO should be
> avoided in the GCC manual. There are many people who would look for
> any excuse to write GCC off as not a serious contender (maintained by
> a bunch of part-time amateurs who can't even write a proper manual,
> they would like to think) so it is important that the official GCC
> documentation be written in a serious tone.
I strongly agree this this statement.
next reply other threads:[~2003-05-20 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 22:58 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-19 0:38 Matt Kraai
2003-05-19 10:35 ` Gerald Pfeifer
2003-05-19 15:07 ` Matt Kraai
2003-05-20 12:01 ` Gerald Pfeifer
2003-05-20 14:12 ` Kelley Cook
2003-05-20 16:14 ` Andrew Haley
2003-05-20 16:43 ` Fergus Henderson
2003-05-20 17:56 ` Gerald Pfeifer
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=20030520220843.556EFF2DA0@nile.gnat.com \
--to=dewar@gnat.com \
--cc=aph@redhat.com \
--cc=fjh@cs.mu.OZ.AU \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).