public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Kevin Grittner <[email protected]>
Cc: Marti Raudsepp <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: [PATCH] Various documentation typo/grammar fixes
Date: Sat, 30 Aug 2014 13:43:26 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CABRT9RA_kHEZrw9W=C_yYpR8+TTLqVMVKUSU0hrLC213cJ4Hyg@mail.gmail.com>
<[email protected]>
<CABRT9RBDUVXJGoVP3CGL2y5JbpqHSGjH1871wPBj3fw+qX_b3g@mail.gmail.com>
<[email protected]>
<CABRT9RCR8XziafHjS=P6DvKxQ2x1T=EnmB4MsLBqwf23byDOig@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
Kevin Grittner <[email protected]> writes:
> Patch 1 pushed, with each fix back-patched as far as the error
> exists in supported releases.� I held off on patch 2 -- partly
> because I spotted at least one case where things weren't quite
> right, partly because there's so much I haven't had time to go over
> it in sufficient detail, and partly because commas are omitted so
> consistently where most style guides want them that I thought
> someone might want to argue that this was an intentional style
> choice and should be preserved.
I would argue against applying patch 2 at all. I think it's what
John McIntyre (http://www.baltimoresun.com/news/language-blog/)
would call peeverism. If there are any places where the extra
commas/periods actually add anything to clarity, then sure, change
those places --- but doing it only because some style guide tells
you to is not the way to approach the issue. We're writing English
not C code here, and so there is no single standard of correctness.
regards, tom lane
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCH] Various documentation typo/grammar fixes
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox