Re: Replace l337sp34k in comments.
От | Peter Geoghegan |
---|---|
Тема | Re: Replace l337sp34k in comments. |
Дата | |
Msg-id | CAH2-Wzmebc7gN4CfeZUoiopENAHp6egAPw-F2OkhZbVueLRPNw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Replace l337sp34k in comments. (Andrey Borodin <x4mmm@yandex-team.ru>) |
Ответы |
Re: Replace l337sp34k in comments.
Re: Replace l337sp34k in comments. |
Список | pgsql-hackers |
On Sat, Jul 31, 2021 at 11:22 AM Andrey Borodin <x4mmm@yandex-team.ru> wrote: > FWIW, my 2 cents. > I do not see much difference between up2date, up-to-date, up to date, current, recent, actual, last, newest, correct, freshetc. +1. To me it seems normal to debate wording/terminology with new code comments, but that's about it. I find this zeal to change old code comments misguided. It's okay if they're clearly wrong or have typos. Anything else is just hypercorrection. And in any case there is a very real chance of making the overall situation worse rather than better. Probably in some subtle but important way. See also: commit 8a47b775a16fb4f1e154c0f319a030498e123164 -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: