Re: Why --backup-and-modify-in-place in perltidy config? - Mailing list pgsql-hackers

From Gavin Flower
Subject Re: Why --backup-and-modify-in-place in perltidy config?
Date
Msg-id 068e72ea-3684-0a55-d619-f7ef8a08d99d@archidevsys.co.nz
Whole thread Raw
In response to Re: Why --backup-and-modify-in-place in perltidy config?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 16/08/16 16:19, Andrew Dunstan wrote:
>
>
> On 08/15/2016 02:23 PM, Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> On 08/15/2016 10:19 AM, Tom Lane wrote:
>>>> Andrew Dunstan <andrew@dunslane.net> writes:
>>>>> We should probably specify -bext='/', which would cause the backup 
>>>>> files
>>>>> to be deleted unless an error occurred.
>>>> Really?  That seems a bit magic, and it's certainly undocumented.
>>> We must be using different versions.
>> Hmm ... I'm using the RHEL6 version, which claims to be v20090616,
>> which is what pgindent/README says to use.
>
>
> Ah. I have Fedora 22's v20140711. 2009 seems a bit ancient :-) Anyway, 
> what you've done seems fine.
>
> cheers
>
> andrew
>
>
>
A vintage year, but for the best taste, it has to have been to be aged 
on Oak!  :-)




pgsql-hackers by date:

Previous
From: Venkata B Nagothi
Date:
Subject: Re: patch proposal
Next
From: Ryan Murphy
Date:
Subject: Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)