Horton

Re: i.e. and e.g.

John Naylor <john.naylor@enterprisedb.com>

View thread View on postgr.es
From: John Naylor <john.naylor@enterprisedb.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-21T05:30:04Z
Lists: pgsql-hackers 
On Thu, Jul 21, 2022 at 11:22 AM Kyotaro Horiguchi <horikyota.ntt@gmail.com>
wrote:
>
> At Thu, 21 Jul 2022 10:20:30 +0700, John Naylor <
john.naylor@enterprisedb.com> wrote in
> > On Wed, Jul 20, 2022 at 3:40 PM Kyotaro Horiguchi <
horikyota.ntt@gmail.com>
> > wrote:
> > > By the way, I forgot about back-branches. Don't we need to fix the
> > > same in back-branches?
> >
> > The intent of the messages is pretty clear to me, so I don't really see
a
> > need to change back branches. It does make sense for v15, though, and I
> > just forgot to consider that.
>
> Ok, I'm fine with that. Thanks!

This is done.

--
John Naylor
EDB: http://www.enterprisedb.com

Commits

  1. Correct some uses of e.g. and i.e. in message strings and documentation