From: | Josh Soref <jsoref(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Possible spelling fixes |
Date: | 2017-03-01 16:38:32 |
Message-ID: | CACZqfqBTd+z9aqOX0q2Va59avLA3BLGeWp0rA0p17df1Khw14Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I understood that they were git commits. I could have excluded the
file but opted not to in case people were willing to take a small
drift -- the SHAs are what someone needs to review the commit, and
personally, I'd rather read something without typos than with --
especially in a summary. But, I'll tentatively exclude the lines
containing SHAs.
do you want:
@@ -3116,7 +3116,7 @@ 2016-02-17 [a5c43b886] Add new system vi
<para>
This view exposes the same information available from
- the <application>pg_config</> comand-line utility,
+ the <application>pg_config</> command-line utility,
namely assorted compile-time configuration information for
<productname>PostgreSQL</>.
</para>
or should I exclude the file entirely?
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Soref | 2017-03-01 16:40:50 | Re: Possible spelling fixes |
Previous Message | Josh Soref | 2017-03-01 16:35:12 | Re: Possible spelling fixes |