From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chao Li <li.evan.chao@gmail.com>
Cc: Rahila Syed <rahilasyed90@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pgindent versus struct members and typedefs
Date: Wed, 6 May 2026 10:15:07 -0500
Message-ID: <afta-6zVawsxlt1v@nathan> (raw)
In-Reply-To: <771696.1778079755@sss.pgh.pa.us>
References: <aS9hkwnkWf3dZIA_@nathan>
<347EA055-D626-414C-B10D-7E70041B9B55@gmail.com>
<509793.1764715875@sss.pgh.pa.us>
<afplW8DvRONDc1yl@nathan>
<729177.1778039019@sss.pgh.pa.us>
<aftTyjC_xWp-n30S@nathan>
<771696.1778079755@sss.pgh.pa.us>
On Wed, May 06, 2026 at 11:02:35AM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> Some of our changes to pg_bsd_indent bumped INDENT_VERSION. Should we do
>> that here?
>
> We already have an INDENT_VERSION bump queued for the
> space-between-comma-and-period change. I don't think we need two
> bumps in this cycle, as long as we coordinate pushing these changes.
Okay. I'll go ahead and commit the patches for $subject then, leaving out
the version bump.
--
nathan
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-hackers@postgresql.org
Cc: nathandbossart@gmail.com, tgl@sss.pgh.pa.us, li.evan.chao@gmail.com, rahilasyed90@gmail.com, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: pgindent versus struct members and typedefs
In-Reply-To: <afta-6zVawsxlt1v@nathan>
* 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