Hi, On Fri, 2003-11-14 at 05:16, Brian Jones wrote: > Michael Koch <[EMAIL PROTECTED]> writes: > > > I think it would be really nice i you could commit this to libgcj too. > > This class is totally merged. > > Just out of my curiosity, how does that whole process work?
libgcj and GNU Classpath are mostly completely merged. Basically people monitor both the classpath-commit and the gcj java-patches mailinglist and pick up patches that have not been approved/committed to both trees. Most libgcj committers also have Classpath commit access and commit their changes to Classpath as soon as they are accepted for libgcj. (libgcj has a good review process that I hope we can adopt in the future for Classpath.) Normally I test almost every change I make against both Classpath (+Kissme) and gcj so that I can commit to both trees at once (after approval on java-patches). At the moment I have a slightly hacked up gcj here so I cannot easily test my patches on gcj so I don't submit patches to them at the moment. And from time to time people go through the following page http://gcc.gnu.org/java/libgcj-classpath-compare.html to see what has not gone into both trees and suggest to merge those things. (Hopefully when kaffe is more merged with Classpath we can have a similar page to compare kaffe-classpath). Michael has been a big help here keeeping Classpath/libgcj in sync. Thanks Michael. Cheers, Mark
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
