Horton

Re: Importing pg_bsd_indent into our source tree

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To:
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2023-02-12T01:43:52Z
Lists: pgsql-hackers

Attachments

I wrote:
> Hmmm ... ci autoconf build is now happy, but the Windows run complains
> that none of the output files match.  I'm betting that this is a
> Windows-newline problem, since I now see that indent.c opens both the
> input and output files in default (text) mode.  I'm inclined to
> change it to open the output file in binary mode while leaving the
> input in text, which should have the effect of stripping \r if it's
> present.

So let's see if that theory is correct at all ...

			regards, tom lane

Commits

  1. Integrate pg_bsd_indent into our build/test infrastructure.

  2. Sync pg_bsd_indent's copyright notices with Postgres practice.

  3. Import pg_bsd_indent sources.