Re: i.e. and e.g.

2022-07-21 Thread Kyotaro Horiguchi
At Thu, 21 Jul 2022 12:30:04 +0700, John Naylor wrote in > On Thu, Jul 21, 2022 at 11:22 AM Kyotaro Horiguchi > wrote: > > > > At Thu, 21 Jul 2022 10:20:30 +0700, John Naylor < > john.nay...@enterprisedb.com> wrote in > > > need to change back branches. It does make sense for v15, though, and I

Re: i.e. and e.g.

2022-07-20 Thread John Naylor
On Thu, Jul 21, 2022 at 11:22 AM Kyotaro Horiguchi wrote: > > At Thu, 21 Jul 2022 10:20:30 +0700, John Naylor < john.nay...@enterprisedb.com> wrote in > > On Wed, Jul 20, 2022 at 3:40 PM Kyotaro Horiguchi < horikyota@gmail.com> > > wrote: > > > By the way, I forgot about back-branches. Don't w

Re: i.e. and e.g.

2022-07-20 Thread Kyotaro Horiguchi
At Thu, 21 Jul 2022 10:20:30 +0700, John Naylor wrote in > On Wed, Jul 20, 2022 at 3:40 PM Kyotaro Horiguchi > 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

Re: i.e. and e.g.

2022-07-20 Thread John Naylor
On Wed, Jul 20, 2022 at 3:40 PM Kyotaro Horiguchi 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

Re: i.e. and e.g.

2022-07-20 Thread Kyotaro Horiguchi
At Thu, 14 Jul 2022 15:38:37 +0900 (JST), Kyotaro Horiguchi wrote in > At Thu, 14 Jul 2022 09:40:25 +0700, John Naylor > wrote in > > On Wed, Jul 13, 2022 at 4:13 PM Kyotaro Horiguchi > > wrote: > > > > > > At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi < > > horikyota@gmail

Re: i.e. and e.g.

2022-07-13 Thread Kyotaro Horiguchi
At Thu, 14 Jul 2022 09:40:25 +0700, John Naylor wrote in > On Wed, Jul 13, 2022 at 4:13 PM Kyotaro Horiguchi > wrote: > > > > At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi < > horikyota@gmail.com> wrote in > > > So, "e.g." (for example) in the message sounds like "that is", wh

Re: i.e. and e.g.

2022-07-13 Thread John Naylor
On Wed, Jul 13, 2022 at 4:13 PM Kyotaro Horiguchi wrote: > > At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi < horikyota@gmail.com> wrote in > > I happened to see the message below. > > > > > WARNING: new data directory should not be inside the old data directory, e.g. %s > > > >

Re: i.e. and e.g.

2022-07-13 Thread Aleksander Alekseev
Hi Kyotaro, > Oops! There's another use of that word in the same context. > Attached contains two fixes. Good catch. I did a quick search for similar messages and apparently there are no others to fix. -- Best regards, Aleksander Alekseev

Re: i.e. and e.g.

2022-07-13 Thread Junwang Zhao
make sense. +1 On Wed, Jul 13, 2022 at 5:14 PM Kyotaro Horiguchi wrote: > > At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi > wrote in > > I happened to see the message below. > > > > > WARNING: new data directory should not be inside the old data directory, > > > e.g. %s > > > >

Re: i.e. and e.g.

2022-07-13 Thread Kyotaro Horiguchi
At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi wrote in > I happened to see the message below. > > > WARNING: new data directory should not be inside the old data directory, > > e.g. %s > > The corresponding code is > > > ... the old data directory, e.g. %s", old_cluster_pgdata

i.e. and e.g.

2022-07-13 Thread Kyotaro Horiguchi
I happened to see the message below. > WARNING: new data directory should not be inside the old data directory, > e.g. %s The corresponding code is > ... the old data directory, e.g. %s", old_cluster_pgdata); So, "e.g." (for example) in the message sounds like "that is", which I think is "i.e