[postgis-devel] Testing astyle rule

[Chris Hodgson]

Perhaps an alternative method would be to implement a 'make 
changes-clean' target that only runs astyle on the files that you've 
modified, as per svn status. Then get everyone to at least commit 
cleaned changes. This should make it less impossible to track changes 
historically and the code will get cleaned up slowly.

Something like:

svn status | cut -c 8- | xargs -n1 astyle {options}

but that's probably not very portable...

Chris

Kevin Neufeld wrote:
> On 1/29/2010 11:50 AM, strk wrote:
>> Is there a plan for how to bring trunk to style-clean state ?
>
> You mean this polarized discussion?
>
> (http://postgis.refractions.net/pipermail/postgis-devel/2010-January/008430.html) 
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel