tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Harner <bobhar...@gmail.com>
Subject Re: svn commit: r1142044 - /tapestry/tapestry5/trunk/support/tapestry_idea_codestyle.xml
Date Sat, 02 Jul 2011 12:04:15 GMT
Unless a file is horribly formatted, or else completely new or almost
completely rewritten, I think reformatting just wastes the time of
others reading the diffs. All of us are capable of overlooking the
"wrong" brace style by now.

On Sat, Jul 2, 2011 at 4:40 AM, Massimo Lusetti <mlusetti@gmail.com> wrote:
> On Fri, Jul 1, 2011 at 10:54 PM, Josh Canfield <joshcanfield@gmail.com> wrote:
>
>> If files are not in line with the code style then they should be
>> reformatted without any other changes (so function changes aren't
>> hidden in format changes).
>>
>> Before I check a file in with changes I'm planning to first reformat
>> it and check it in. Should we have a tracking issue for these types of
>> checkins? or is that as pointless as it sounds?
>
> Not at all, it would be great to have style(9) and a complete adherence.
> This policy sounds great to my ears.
>
> Cheers
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message