[FYI] new branch "java-gui-branch"

[graydon hoare <graydon at redhat dot com>]

hi,

I've been talking recently with some of the other Red Hat people tasked 
with working on java GUI technology -- AWT and Swing -- and we've come 
to the conclusion that this work would be accelerated a bit if we 
temporarily relocated to a secondary branch, the goal being to improve 
the inter-group communication and minimize idle time associated with 
mainline's (rightly) conservative review and approval process.

unless someone has a serious objection, I would like the rules for this 
branch to be as follows: you can commit your work without per-patch 
review, assuming you're patching or adding files you're "supposed" to be 
working on (in java/awt, gnu/java/awt, javax/swing, etc.), but please 
continue to send patches showing the changes you make to 
java-patches@gcc.gnu.org, so that interested parties can review your 
work chronologically.

we'll do bulk merges back into the mainline (and classpath) once the 
activity settles down a bit, but at somewhat larger intervals. if you 
commit code which breaks, we'll sort it out on IRC or mailing lists. the 
intention here is to try to build up the GUI libraries *fast*, and 
communicate all our work to one another as quickly as possible.

this branch only applies to the gcc/libjava module; to move your working 
copy to this branch, do the following:

$ cd $SRCDIR/gcc/libjava
$ cvs update -r java-gui-branch

you can check to see that your files moved to the new branch using the
"cvs status" command, as such:

$ cvs status Makefile.am
===================================================================
File: Makefile.am       Status: Up-to-date

   Working revision:    1.361
   Repository revision: 1.361   /cvs/gcc/gcc/libjava/Makefile.am,v
   Sticky Tag:          java-gui-branch (branch: 1.361.2)
   Sticky Date:         (none)
   Sticky Options:      (none)

the thing to look for being the "sticky tag", set to java-gui-branch.

-graydon