From: Michael Paquier <michael@paquier.xyz>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix code indentation violations introduced by recent commit
Date: Fri, 11 Aug 2023 11:49:03 +0000
Message-ID: <E1qUQda-001Wfp-GS@gemulon.postgresql.org> (raw)
Fix code indentation violations introduced by recent commit
The two culprit commits are 5765cfe and 5e0c761.
Per buildfarm member koel for the first commit, while I have noticed the
second one in passing.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/5dc456b7dda4f7d0d7735b066607c190c74d174a
Modified Files
--------------
src/backend/utils/fmgr/fmgr.c | 15 ++++++++-------
src/backend/utils/misc/guc.c | 12 ++++++------
src/bin/pgbench/pgbench.c | 2 +-
3 files changed, 15 insertions(+), 14 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: michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix code indentation violations introduced by recent commit
In-Reply-To: <E1qUQda-001Wfp-GS@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