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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Why --backup-and-modify-in-place in perltidy config?
Дата
Msg-id 19914.1471285423@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Why --backup-and-modify-in-place in perltidy config?  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Why --backup-and-modify-in-place in perltidy config?  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
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.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Shay Rojansky
Дата:
Сообщение: Re: Slowness of extended protocol
Следующее
От: Tom Lane
Дата:
Сообщение: Let's get rid of the separate minor version numbers for shlibs