Re: Hint and detail punctuation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Hint and detail punctuation
Date: 2019-01-21 21:01:07
Message-ID: 20190121210107.GC1060@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 5, 2018 at 05:22:25PM +0100, Daniel Gustafsson wrote:
> While looking at error messages downstream, I noticed a few hints and details
> in postgres which aren’t punctuated as per the style guide. The attached patch
> fixes the ones where it seemed reasonable to end with a period.

FYI, this was applied:

commit 730422afcdb6784bbe20efc65de72156d470b0c4
Author: Michael Paquier <michael(at)paquier(dot)xyz>
Date: Fri Dec 7 07:47:42 2018 +0900

Fix some errhint and errdetail strings missing a period

As per the error message style guide of the documentation, those should
be full sentences.

Author: Daniel Gustafsson
Reviewed-by: Michael Paquier, Álvaro Herrera
Discussion: https://1E8D49B4-16BC-4420-B4ED-58501D9E076B(at)yesql(dot)se

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-01-21 21:19:54 Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
Previous Message Fabien COELHO 2019-01-21 20:57:09 Re: Alternative to \copy in psql modelled after \g