Just to throw in another twist, how about a batch process that periodically checks out and formats all of the code ? This way the formatting changes would be isolated from real code changes.
Nick -----Original Message----- From: David Graham [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 5:26 PM To: [EMAIL PROTECTED] Subject: Re: Struts Coding Standard Couldn't you do it just on check-in? It seems like it would take forever to check out the project if it's always formatting the code. Dave >From: Robert Leland <[EMAIL PROTECTED]> >Reply-To: "Struts Developers List" <[EMAIL PROTECTED]> >To: Struts Developers List <[EMAIL PROTECTED]> >Subject: Re: Struts Coding Standard >Date: Mon, 06 Jan 2003 17:11:41 -0500 > >Craig R. McClanahan wrote: >>the functional changes, and created a lot >>of "noise" in the commit diffs. You'd think this would go away after each >>file has been checked out and updated at least once, but that never really >>seems to happen (because the formatting rules often get tweaked). > >That is why I had suggested that the files get formatted on >checkout & checkin then doing a diff always works. > >-Rob > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?page=features/virus -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
