aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--libjava/ChangeLog4
-rw-r--r--libjava/HACKING8
2 files changed, 10 insertions, 2 deletions
diff --git a/libjava/ChangeLog b/libjava/ChangeLog
index cc3d33f..a058dc5 100644
--- 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 3f96b6f..6ea549d 100644
--- 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>