public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Fergus Henderson <fjh@cs.mu.OZ.AU>
Cc: Andrew Haley <aph@redhat.com>, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: "obvious" requirements
Date: Tue, 20 May 2003 17:56:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.55.0305201922150.44542@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030520163654.GA16094@ceres.cs.mu.oz.au>

On Wed, 21 May 2003, Fergus Henderson wrote:
> On 20-May-2003, Andrew Haley <aph@redhat.com> wrote:
>> "anal" is not a vulgarity, but a reference to Sigmund Freud's ideas on
>> anality, first published in 1908. Freud wrote that people with "anal
>> character" were meticulous, parsimonious, and obstinate.

This may be related to me living less than 10km away from Berggasse 16 and
Andrew living near London (IIRC) ;-), but I don't see a problem either.

Even more so considering that it's not in the manual but one of the
web pages for those with GCC CVS write access, and has been there for
nearly five years:

  revision 1.3 of checkin.html
  date: 1998/07/05 22:37:42;  author: law;  state: Exp;  lines: +8 -2
  Note not to modify the guile subdir.  Also note certain changes that do
  not need approval for checkins.

I have, however, installed the following clarification below for now.

Gerald

Index: cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.52
diff -u -3 -p -r1.52 cvswrite.html
--- cvswrite.html	26 Mar 2003 21:18:35 -0000	1.52
+++ cvswrite.html	20 May 2003 17:48:14 -0000
@@ -135,7 +135,7 @@ in the MAINTAINERS file in the GCC distr

 <p>Also note that fixes for obvious typos in ChangeLog files, docs,
 web pages, comments and similar stuff need not be approved.  Just
-check in the fix.  We don't want to get overly anal about checkin
+check in the fix.  We don't want to get overly anal-retentive about checkin
 policies.</p>

 <p>When you have checked in a patch exactly as it has been approved,

  reply	other threads:[~2003-05-20 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2003-05-20 22:58 Robert Dewar

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=Pine.BSF.4.55.0305201922150.44542@acrux.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --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).