public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Liudmila Mantrova <[email protected]>
Cc: [email protected]
Subject: Re: Misc typos in documentation
Date: Thu, 6 Sep 2018 20:43:11 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CABUevEw99tzsCuTO9OnyYLW0z_OvMip=TGNXmuhhomhSGvfkcQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
On Thu, Sep 6, 2018 at 06:45:29PM +0300, Liudmila Mantrova wrote:
>
> On 08/25/2018 10:04 PM, Bruce Momjian wrote:
> >On Thu, Aug 16, 2018 at 11:25:25AM +0300, Liudmila Mantrova wrote:
> >>On 06/20/2018 05:04 PM, Magnus Hagander wrote:
> >> I have split them in two just in case rn-typos.patch conflicts with any
> >> current work on release-11.sgml, which seems to be going on in more
> >> than one thread. I'll appreciate your feedback if it should have been
> >> done differently.
> >>
> >>I have bumped into a couple of similar typos in 9.6 and 10 - the patch based on
> >>REL9_6_STABLE is attached.
> >I have made the adjustments to 9.6 and 10 as you suggested. I added
> >quoting to "two" to match other releases:
> >
> > https://git.postgresql.org/pg/commitdiff/993b5a78adff29fc58e7449cab98bb865b77c663
> >
> >Thanks.
> >
> Thank you, Bruce!
>
> I totally missed those quotes (and your response).
> I've just noticed your recent commit, and looks like the typo to be fixed
> ("boundries") managed to escape somehow.
> Assuming it's not an alternative spelling I'm unaware of, I'm attaching a
> smaller version of the patch (based on the current state of REL_10_STABLE).
Oh, yes, I missed that. Applied to PG 9.6 and 10, which is where they
were needed. Thanks.
--
Bruce Momjian <[email protected]> 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 +
view thread (6+ messages)
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: Misc typos in documentation
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