pgsql: Clarify some comments making use of leetspeak term "up2date"

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clarify some comments making use of leetspeak term "up2date"
Date: 2021-07-28 01:32:16
Message-ID: E1m8YQi-00083A-1X@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clarify some comments making use of leetspeak term "up2date"

Most of these are new, as of a8fd13c, and "up-to-date" is much easier to
parse for the average reader.

Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+PtHbHvgOjs_R9LyDF21j-Wn8SxoTtWMQNP2ifXN6t2cSg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/7b7fbe1e8bb4b2a244d1faa618789db411316e55

Modified Files
--------------
src/backend/jit/llvm/llvmjit_expr.c | 2 +-
src/backend/replication/logical/logical.c | 24 ++++++++++++------------
2 files changed, 13 insertions(+), 13 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2021-07-28 03:03:01 pgsql: Doc: Clarify lock levels taken during ATTACH PARTITION
Previous Message Michael Paquier 2021-07-28 01:11:49 pgsql: Add support for SET ACCESS METHOD in ALTER TABLE