Hi Andrew, Wed, 17 Oct 2012 03:46:19 -0400 (EDT) от Andrew Hughes <gnu.and...@redhat.com>: >----- Original Message ----- > > Hi Andrew, > > > > Sun, 14 Oct 2012 17:02:52 -0400 (EDT) от Andrew Hughes > > <ahug...@redhat.com>: > > > Because he actually wants them to be included in GNU Classpath. > > > > On Tue, 16 Oct 2012, Ivan Maidanski wrote: > > > Can't understand. There are GNU Classpath development branches? > > > > I guess what Andrew is trying to say here is that I work against GNU > > Classpath master and submit changes for review and inclusion very > > aggressively. > > > > That pretty much avoids the problem you're having with a huge backlog > > of > > unreviewed changes. ;-) > > > > What am I saying is it's fine to develop on a branch, of course, but if you > actually want the work included in a release, it has to be on trunk/HEAD/whatever. So, you recommend me to put the patches I've prepared to SVN trunk/HEAD? Are we still going to support SVN? (It seems I don't I understand your "it has to be on".)
> > If you're familiar with how Linux is developed, it's like fixing it in one of the > subsystem trees, or linux-next, but never asking Linus to pull it into his tree > for the next release. Heard of. Every vendor has its own patched Linux. But I don't understand why you are referring to? Activity at Linux git significantly differs from that of Classpath, pulling policy differs as well and I don't think you going to match. Anyway, as you already noticed, the patches are at a branch on a github - anyone could checkout and cherry-pick. Regards, Ivan > > > Pekka > > -- > Andrew :) > > Free Java Software Engineer > Red Hat, Inc. (http://www.redhat.com) > > PGP Key: 248BDC07 (https://keys.indymedia.org/) > Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 > >
