Re: i.e. and e.g.
Junwang Zhao <zhjwpku@gmail.com>
From: Junwang Zhao <zhjwpku@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2022-07-13T09:21:20Z
Lists: 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
Commits
-
Correct some uses of e.g. and i.e. in message strings and documentation
- 82785effc01d 16.0 landed