JDK 7 moving to mercurial -- svn repositories

Mark Wielaard mark at klomp.org
Tue Oct 30 11:14:12 UTC 2007

Hi Kelly,

On Mon, 2007-10-29 at 13:44 -0700, Kelly O'Hair wrote:
> But the granularity of the change history is incomplete between the
> OpenJDK subversion and icedtea mercurial repositories.

The granularity is the same between the systems. The Mercurial
repository contains the exact same change history as the subversion

> All information about who made a change or why the change was made
> has been lost in the subversion repository, all you have are all the changes
> made between promotions, all munged together with no changesets for bug
> fixes or feature additions.

Sure, but that is all we hackers have for the moment. If the other SCM
doesn't provide more information than that then that is what we have to
work with. It is still useful information if you are searching for
changes between openjdk b[x] and b[y] to track down a bug introduced
between versions.

> Accurate SCM changesets should record the correct date/time the changeset
> was created, and by who, and include the specific comments added by the
> engineer making the change. This is difficult to get right when transitioning
> history between SCM's.

I don't believe it is that hard to transition history between SCMs. At
least not if it is between modern ones like subversion and mercurial
(CVS is explicitly excluded). Yes, incomplete information in, means
incomplete information out. If you could introduce that extra
information into the subversion repo it is easy to pick it up in the
mercurial repo. If not, then we manage with what we have.

All I am saying is that incomplete information is better than no
information if you are tracking down stuff in your SCM of choice,
whether it is subversion, mercurial or something else.



More information about the discuss mailing list