Re: i.e. and e.g.

From: Junwang Zhao <zhjwpku(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: i.e. and e.g.
Date: 2022-07-13 09:21:20
Message-ID: CAEG8a3KGLx0WW+nHXuk+bj3EgyczZxMrTwobDvomtSayF47KJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

make sense.

+1

On Wed, Jul 13, 2022 at 5:14 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)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
> >
> > 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.". It should be fixed if this is correct. I'm not sure
> > whether to keep using Latin-origin acronyms like this, but in the
> > attached I used "i.e.".
>
> Oops! There's another use of that word in the same context.
> Attached contains two fixes.
>
> regards.
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center

--
Regards
Junwang Zhao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2022-07-13 09:25:32 Re: i.e. and e.g.
Previous Message Kyotaro Horiguchi 2022-07-13 09:13:51 Re: i.e. and e.g.