From: Andrew Dunstan <andrew@dunslane.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Subject: Re: pgindent run coming
Date: Sat, 13 Jun 2009 09:33:59 -0400
Message-ID: <4A33AAC7.2000008@dunslane.net> (raw)
In-Reply-To: <200906131613.53870.peter_e@gmx.net>
References: <200906101950.n5AJoFP01545@momjian.us>
<200906102344.53483.peter_e@gmx.net>
<13137.1244667281@sss.pgh.pa.us>
<200906131613.53870.peter_e@gmx.net>
Peter Eisentraut wrote:
> On Wednesday 10 June 2009 23:54:41 Tom Lane wrote:
>
>> Peter Eisentraut <peter_e@gmx.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, peter_e@gmx.net, tgl@sss.pgh.pa.us, bruce@momjian.us
Subject: Re: pgindent run coming
In-Reply-To: <4A33AAC7.2000008@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox