| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: pgindent run coming |
| Date: | 2009-06-13 13:33:59 |
| Message-ID: | 4A33AAC7.2000008@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On Wednesday 10 June 2009 23:54:41 Tom Lane wrote:
>
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>
>>>>> I think it usually does that already ...
>>>>>
>>> Um, attached you will find a bunch of counterexamples.
>>>
>> At a quick look, I'm not sure that any of these are in code that hasn't
>> been edited since the 8.3 pgindent run.
>>
>
> So what does that mean then? Surely pgindent doesn't keep track of what has
> been edited when?
>
>
If the code has been edited since the last pgindent run, then pgindent
hasn't had a chance to adjust it, no?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-13 13:57:59 | Re: pgindent run coming |
| Previous Message | Peter Eisentraut | 2009-06-13 13:13:52 | Re: pgindent run coming |