On Wed, Dec 8, 2010 at 1:53 AM, Dr Andrew John Hughes <gnu_andrew@xxxxxxxxxxxxxx> wrote: >> As soon as I am back I would like us to at least start moving to >> mercurial on savannah if people don't mind. > > Yes, I do mind. > > We already discussed this some time back: > > http://developer.classpath.org/pipermail/classpath/2008-June/002629.html > > and nothing happened. I don't particularly see any huge benefit to > moving the repository to a different version control system. It would > make more sense if there were lots of contributors but there aren't. > As is, if you're going to put some time in, I'd rather it was spent > reviewing patches than messing about with the VCS. > > One of Pekka's motivations is also flawed: > > 'how much problems it causes for developers that don't have commit > rights to the centralized repository!' > > Moving it all to Mercurial just so it's easier for someone else to > create a forked lower-quality copy that accepts unreviewed patches is > not a good motivation IMHO. > > The discussion earlier today: > > http://developer.classpath.org/pipermail/classpath-patches/2010-December/006528.html > > shows exactly why we do need patch review and discussion. No, no, that's not my motivation at all. Have you used Mercurial or git? CVS make local *development* unnecessary hard. I'm not trying to bypass the review process (which is a great thing!) with a tool. I just find it utterly silly that I need to manually create a git mirror of your CVS repository to make development experience sane. Pekka