On Tue, 2 Nov 2010, Ian Lance Taylor wrote: > > I presume you will be posting the front end and other changes for review > > (or, I suppose, given the size of the changes, explicitly stating that you > > propose for review the diffs between particular revisions of trunk and a > > branch given by a particular svn diff command) as indicated in > > <http://gcc.gnu.org/ml/gcc/2010-01/msg00504.html>. > > I will post all changes outside of the gcc/go and libgo directories for > review, certainly. I would also appreciate review for the code in > gcc/go and libgo on the branch. Whether review is required for that > code is an interesting question. I have been assuming that I would > become the initial maintainer for the gcc/go and libgo directories. As > such, I would be permitted to make changes to those directories without > review. So is review required for the initial checkin? I don't know.
I think new front ends should be reviewed for general style, coding conventions, use of deprecated interfaces, unportabilities etc., just as new back ends should be reviewed. -- Joseph S. Myers jos...@codesourcery.com
