GCC 3.3 Branch

[Mark Mitchell <mark at codesourcery dot com>]

The commands to create the branch are running.  I won't get to all of
the steps in branching.html today; that will happen tomorrow.  

Per Zack's request, the mainline is now under his control.  Zack will
merge the basic-improvements branch to the mainline and ensure all is
well, and then send out a message announcing that.  If Zack's still at
work, that might happen tonight; otherwise, it will happen later.
Zack, the world will keep spinning if this takes a while; don't kill
yourself getting it done.  :-)

Until Zack gives the OK, the mainline is still frozen.  Once Zack
gives the OK, the mainline is open under the usual rules: all approved
patches are OK, if they don't cause regressions.  I'd prefer that we
phase in the merging of any major branches, rather than trying to do
that all at once; let's coordinate that by announcing the intention to
merge a branch at least 24 hours in advance of the actual merge, and
avoid doing more than one within a couple of days of each other.

Zack, it may take a few minutes for the "cvs rtag" commands to run
through.  Once you see "gcc-3_3-branch" tags on files, it's done.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com