Re: Equivalent of --enable-tap-tests in MSVC scripts - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Equivalent of --enable-tap-tests in MSVC scripts
Date
Msg-id CAMsr+YGvSsrWU4eUZNZOu6SqqcpJdqbgidar8dA37ucLXb=PZQ@mail.gmail.com
Whole thread Raw
In response to Re: Equivalent of --enable-tap-tests in MSVC scripts  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Equivalent of --enable-tap-tests in MSVC scripts
List pgsql-hackers
On 5 March 2016 at 00:10, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Craig Ringer wrote:

> If it's the result of perltidy changing its mind about the formatting as a
> result of this change I guess we have to eyeroll and live with it. perltidy
> leaves the file alone as it is in the tree currently, so that be it.
>
> Gripe withdrawn, ready for committer IMO

Okay, thanks.  I applied it back to 9.4, which is when
--enable-tap-tests appeared.  I didn't perltidy 9.4's config_default.pl,
though.

Thanks very much. It didn't occur to me to backport it, but it seems harmless.


--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: postgres_fdw vs. force_parallel_mode on ppc
Next
From: Tom Lane
Date:
Subject: Re: postgres_fdw vs. force_parallel_mode on ppc