2003-03-26 Vladimir Makarov <vmakarov@redhat.com>

[pf3gnuchains/gcc-fork.git] / libjava / HACKING

diff --git a/libjava/HACKING b/libjava/HACKING
index 842617a..f0ad859 100644 (file)
--- a/libjava/HACKING
+++ b/libjava/HACKING
@@ -18,8 +18,12 @@ efficient, cleanest) implementation of each method/class/package, resolve
 any conflicts created by the merge, and test the final result.
 
 The merged files can be recognized by the standard Classpath copyright
-comments at the top of the file. If you make changes to these files then
-you should also send a patch to the classpath mailinglist.
+comments at the top of the file. If you make changes to these files
+then you should also check in the fix to Classpath.  For small changes
+it may be easier to send a patch to the classpath mailinglist.  For
+large changes, if you have direct write access to the libgcj tree,
+then you will also need to get a Classpath account and do the work
+yourself.
 <http://mail.gnu.org/mailman/listinfo/classpath/>
 <mailto:classpath@gnu.org>
 
@@ -38,9 +42,9 @@ But note the following (thanks to Bryce McKinlay):
 > Makefile?
 Yup, you need the magic libgcj automake ;-)
 
-<ftp://ftp.freesoftware.com/.0/sourceware/java/automake-gcj-1.4.tar.gz>
+<ftp://sources.redhat.com/pub/java/automake-gcj-1.4.tar.gz>
 
-Install that (dont worry, it should still work for other projects), add your
+Install that (don't worry, it should still work for other projects), add your
 files to the Makefile.am, then just type "automake" and it will regenerate the
 Makefile.in. Easy!