* HACKING: Make people commit their own patches.

From-SVN: r46816

diff --git a/libjava/ChangeLog b/libjava/ChangeLog
index cc3d33faeb3a955d05def8a89be8f7fb19018e9e..a058dc5a9e7c0d58904e3848cbeee61f53ff1dd0 100644 (file)
--- a/libjava/ChangeLog
+++ b/libjava/ChangeLog
@@ -1,3 +1,7 @@
+2001-11-06  Tom Tromey  <tromey@redhat.com>
+
+       * HACKING: Make people commit their own patches.
+
 2001-11-05  Tom Tromey  <tromey@redhat.com>
 
        * java/lang/Class.h (Class): Made _Jv_BytecodeVerifier a friend.

diff --git a/libjava/HACKING b/libjava/HACKING
index 3f96b6f452996e559c1c11c1349d6fd90305b7fb..6ea549daef9e1e6f8418668e564cf3ecd896a8ab 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>