[postgis-devel] astyle

[Paul Ramsey]

On Wed, Jan 27, 2010 at 8:31 AM, Mark Cave-Ayland
<mark.cave-ayland at siriusit.co.uk> wrote:

>> Besides this is something that doesn't change the API so can be done any
>> time.  I fail to see the sense of urgency in this.
>
> Because it sanitises the codebase from the release point while not changing
> the logic in any way.

As Mark notes, the importance here is *when* the change is done. If we
do it before branching, we get the same formatted code in both the
trunk going forward and the maintenance branch too; a boon for
back-porting.

I would like to do this, I'll do it before the next
final-final-really-we-mean-it-and-we-are-the-psc-so-we-promise-to-test-really
internal 1.5.0 tar ball release, then we can see for certain that, in
fact, nothing changes behaviorally.

P