Mercurial repo for openjdk6 drops
Andrew John Hughes
gnu_andrew at member.fsf.org
Wed Sep 17 15:04:19 PDT 2008
2008/9/17 Mark Wielaard <mark at klomp.org>:
> Hi Joe,
> On Tue, 2008-09-16 at 09:37 -0700, Joseph D. Darcy wrote:
>> While I'm sympathetic to the request and appreciate the offer of help,
>> it is unlikely I'll be able to publish the initial Mercurial
>> repositories with any history. The most history that could be published
>> dates back to when OpenJDK 6 branched off from the already open sourced
>> JDK 7. The total amount of bugs fixed from then until now is on the
>> order of 400-500, with somewhat fewer logical changesets. This number
>> of changesets is quite small compared to the amount of pre-Mercurial
>> history that is not being published externally at all.
> That is actually about half of what jdk7 or icedtea (disregarding
> openjdk import changes) have been seeing. So I do think it is a
> significant amount of changes. It would certain help with getting a
> better view of how changes relate to each other.
>> However, the
>> number is large enough that is would be troublesome for me to reliably
>> synthesize changesets. I don't have Martin's process for scripting and
>> SCM hackery and one of the limitation of the teamware SCM is that the
>> changes are only really tracked on a per-file basis. Published
>> truncated teamware histories outside of Sun's firewall for people to
>> help cons up changesets might be technically possible, but much of the
>> prep work and reviews would have to be done internally and the
>> costs/benefits on that portion don't look attractive to me.
> Ah, that is a bummer. I had assumed that the teamware history only
> included stuff starting with the public release of openjdk7. Isn't there
> any way to "replay" the patches starting at that point and post those?
> rcs and cvs also maintain history on a per-file basis, but with some
> scripting tricks it is still possible to reconstruct cross-file
> changesets from them mostly. If that is impossible, could you start
> posting patches to the jdk6-dev when you apply them to your repository?
> So the chunks are smaller and can be commented on more timely than when
> you do full bxx code drops?
Seconded. If you posted patchsets as things are developed, we could
maintain them in our Mercurial repository until such time as a Sun OpenJDK6 one
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev