Re: Why --backup-and-modify-in-place in perltidy config?

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Why --backup-and-modify-in-place in perltidy config?
Date: 2016-08-16 05:46:49
Message-ID: 068e72ea-3684-0a55-d619-f7ef8a08d99d@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16/08/16 16:19, Andrew Dunstan wrote:
>
>
> On 08/15/2016 02:23 PM, Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> On 08/15/2016 10:19 AM, Tom Lane wrote:
>>>> Andrew Dunstan <andrew(at)dunslane(dot)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! :-)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ryan Murphy 2016-08-16 06:02:47 Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)
Previous Message Venkata B Nagothi 2016-08-16 05:08:25 Re: patch proposal