Re: automating perl compile time checking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automating perl compile time checking
Date: 2018-06-11 20:25:21
Message-ID: 22559.1528748721@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 06/11/2018 04:01 PM, Peter Eisentraut wrote:
>> Why is this being committed after feature freeze?

> This affects pretty much nothing. In fact some of the other changes I've
> recently committed were arguably more dangerous. Do you want me to
> revert the whole lot?

AFAICS this is adding testing, not "features", so it seems fine from here.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arthur Zakirov 2018-06-11 20:35:51 Re: adding tab completions
Previous Message Robbie Harwood 2018-06-11 20:11:10 Re: [PATCH v18] GSSAPI encryption support