Re: Add "format" target to make and ninja to run pgindent and pgperltidy
| От | Tom Lane |
|---|---|
| Тема | Re: Add "format" target to make and ninja to run pgindent and pgperltidy |
| Дата | |
| Msg-id | 3913298.1767194804@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Add "format" target to make and ninja to run pgindent and pgperltidy (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>) |
| Ответы |
Re: Add "format" target to make and ninja to run pgindent and pgperltidy
Re: Add "format" target to make and ninja to run pgindent and pgperltidy |
| Список | pgsql-hackers |
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> writes:
> On Wed, Dec 31, 2025 at 5:06 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>> This tries to make running formatting a lot easier for committers, but
>> primarily for new contributors.
> I generally like the idea. Since perltidy is not enforced regularly
> (like pgindent), running it usually ends up modifying files which are
> not part of the patch. So I avoid it if not necessary. Do you propose
> to make it optional?
The other obstacle is that not everybody will have the right version
of perltidy installed, but using some other version will create a
whole lot of extraneous noise.
On the whole I'd recommend not trying to automate the perltidy
step yet. Cost/benefit is just not very good.
On the substance of the patch: I wonder whether we could make things
more reliable by using git metadata to figure out which .h and .c
files to point pgindent at.
regards, tom lane
В списке pgsql-hackers по дате отправления: