*+1 global reformatting. * *I am new to this but what I was thinking was to have a formatted style that is for the project and then one for my own coding taste. When I checkout/update, I would reformat it to my specifications/style. Once I am done with the fix, I would then reformat it to the project standards. Of course, if it is a tiny fix, I wouldn't worry about formating. But this way, when doing diffs you wouldn't see the format changes. However, until I am a actual committer, whoever checks in my change would do what the do (I guess). *
*Calvin * *On Saturday, January 7, 2012, Iwo Banaś <bana...@gmail.com> wrote: * *That's why I'd give +1 for initial global reformatting. I'd also keep the format as similar to the current standard as possible to minimize the changes. * *Cheers, Iwo Banas * I am new to the mailing list and was catching up on all the previous email threads. Was there any decision on a one time global reformatting once the Flex code base is checked in? The source code will be available to us any minute and I wanted to make sure that this important step is done before we start working on more cool stuff :-) On a similar note, is there a document where we have a list of TODOs? I know that JIRA is just about to be set up, but just checking if I am missing some other place. Regards, Om
