| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replace l337sp34k in comments. |
| Date: | 2021-07-31 09:15:34 |
| Message-ID: | CAH2-Wzmebc7gN4CfeZUoiopENAHp6egAPw-F2OkhZbVueLRPNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 31, 2021 at 11:22 AM Andrey Borodin <x4mmm(at)yandex-team(dot)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, fresh etc.
+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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-07-31 10:43:08 | Re: [HACKERS] logical decoding of two-phase transactions |
| Previous Message | Andrey Borodin | 2021-07-31 08:21:58 | Re: Replace l337sp34k in comments. |