FYI: Some new maintainers

[Tom Tromey]

The gcj project had several people with write access of various
kinds.  We more or less followed the gcc model of blanket write
access, maintainerships, and write-after-approval.

Actually our process was set up so that people who wrote pieces of
code, or hacked a certain piece of code often enough, simply assumed
write-without-asking privilege for that code.  There's no clear way to
encode this breakdown into the MAINTAINERS file, so I'm just going to
list the gcj hackers as "write after approval".

I'm setting things up so that Java hackers have the same privileges
they had before the repository merge.  I trust this won't be
controversial.

For reference, here are the people who had gcj access but do not yet
have gcc access:

krab  Kresten Krab Thorup
   Wrote the Java bytecode interpreter in libgcj

brads Bradley Schatz
   Did some web work for gcj

hboehm Hans Boehm
   Wrote and continues to maintain the garbage collector

mark  Mark Wielaard
   Works on various things, mostly relating to merging code with
   Classpath

rolfwr Rolf Rasmussen
   Mostly works on AWT and Java2D

Tom