Re: i.e. and e.g.

Поиск
Список
Период
Сортировка
От Junwang Zhao
Тема Re: i.e. and e.g.
Дата
Msg-id CAEG8a3KGLx0WW+nHXuk+bj3EgyczZxMrTwobDvomtSayF47KJg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: i.e. and e.g.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: i.e. and e.g.  (Aleksander Alekseev <aleksander@timescale.com>)
Список pgsql-hackers
make sense.

+1

On Wed, Jul 13, 2022 at 5:14 PM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
>
> At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@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
> >
> > 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: i.e. and e.g.
Следующее
От: Aleksander Alekseev
Дата:
Сообщение: Re: i.e. and e.g.