One alternative to mass-reformatting is to improve the style checker. There are many cases not covered by it today: http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/style/checkers/cpp.py
On Mon, Feb 18, 2013 at 3:30 PM, Simon Fraser <simon.fra...@apple.com>wrote: > > On Feb 18, 2013, at 2:45 PM, Jason Anderssen <janders...@exactal.com> > wrote: > > Hi all, > > With a background in development (both windows and MAC) I was wanting to > get involved in an open source project that I believe is going to make the > world a greater place. So I have decided to get involved with the WebKit > project. > I would like to start of by performing the boring work of reformatting > code to suite the guidelines as stipulated on the webkit.org website (and > double check that they are still up to date), and would like > recommendations to which parts of the project could do with the > re-formatting first up. ( I feel this will get me to know the framework, > and structure of the code base well, before I can start inputting my coding > and help. ) > > Any feedback to where to start would be very much appreciated > > > We actually shy away from mass code reformatting. It obscures useful > revision history. It's fine to reformat code for code you're actually > changing, but reformatting for the sake of reformatting isn't useful, and > may be harmful. > > Simon > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
