diff options
| author | Tom Tromey <tromey@redhat.com> | 2001-11-07 01:19:20 +0000 |
|---|---|---|
| committer | Tom Tromey <tromey@redhat.com> | 2001-11-07 01:19:20 +0000 |
| commit | 4ebab5dbb33b654269d52aaefff00406699b61a1 (patch) | |
| tree | fce08e3e220edc42fd34f15cb07b886de2e55e7c /libjava/HACKING | |
| parent | af01ae6a54a68eb34db4d7b8cfe27574abc3fa8d (diff) | |
* HACKING: Make people commit their own patches.
git-svn-id: https://gcc.gnu.org/svn/gcc/trunk@46816 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libjava/HACKING')
| -rw-r--r-- | libjava/HACKING | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/libjava/HACKING b/libjava/HACKING index 3f96b6f4529..6ea549daef9 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> |