tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Massimo Lusetti <mluse...@gmail.com>
Subject Re: svn commit: r1142044 - /tapestry/tapestry5/trunk/support/tapestry_idea_codestyle.xml
Date Sat, 02 Jul 2011 08:40:39 GMT
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.


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

View raw message