From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Change example in pgindent README on "/*-----" comments.
Date: Wed, 05 Jul 2023 07:03:06 +0000
Message-ID: <E1qGwXa-001zSc-6W@gemulon.postgresql.org> (raw)
Change example in pgindent README on "/*-----" comments.
Most, but not all, of our "/*----" style comments have an end-guard
line with dashes at the end of the comment. However, pgindent doesn't
care about the end-guards, so they mostly just waste screen
space. Going forward, let's not require end-guards.
Remove a broken end-guard in a comment in walsender.c that led me to
think about this. Remove the end guard from another comment in
walsender.c for consistency, so that we use the same style in all
comments in the file.
However, we have thousands of existing "/*----" comments the repository,
so it's not worth the code churn to change them all.
Discussion: https://www.postgresql.org/message-id/fb083c91-d490-3b65-25f3-05e9118b6b0d%40iki.fi
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/5e8068f04e13e12c182eca3e64ac4377e0c93a5d
Modified Files
--------------
src/backend/replication/walsender.c | 3 +--
src/tools/pgindent/README | 1 -
2 files changed, 1 insertion(+), 3 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: heikki.linnakangas@iki.fi, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Change example in pgindent README on "/*-----" comments.
In-Reply-To: <E1qGwXa-001zSc-6W@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox