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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: 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 04:19:51
Message-ID: 57B29467.4080501@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adam Brusselback 2016-08-16 04:39:32 Re: C++ port of Postgres
Previous Message Tom Lane 2016-08-16 03:12:58 Re: anyelement -> anyrange