Isn't that going to make version to version diffs really difficult to wade through?
Patches will have the same problem, won't they? Maybe a reformat-only version, followed by the version that contains the changes that you really wanted to make in the first place? On 9/13/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > > i say we go completely to the new style. so any time you open up a file > and make any edits you can reformat the entire file. > > -- Allen > > > Anil Gangolli wrote: > > > > > A question about how we are executing on this: > > > > Do we apply it only on new files, retaining old style in old files? > > > > Or do we apply it to old files as we modify old files as well. > > > > Since my IDE formats code for me (as probably for most of us), but > > allows only one setting per project, it's actually easier for me to go > > to a new style completely. > > > > > > --a. > > > > > > ----- Original Message ----- From: "Allen Gilliland" > > <[EMAIL PROTECTED]> > > To: "roller-dev" <roller-dev@incubator.apache.org> > > Sent: Monday, September 12, 2005 9:40 AM > > Subject: Re: code conventions (recap requested) > > > > > >> I think we settled on K&R > >> > >> -- Allen > >> > >> > >> On Sun, 2005-09-11 at 10:50, Anil Gangolli wrote: > >> > >>> The final result of the recent (several weeks ago) code conventions > >>> vote seems not to have been declared, or I missed it. > >>> > >>> Should we be using K&R brace style (or Sun conventions) for all new > >>> files now? > >>> > >>> --a. > >>> > >>> > >>> > > >
