RFC: migrating to git

Roman Leshchinskiy rl at cse.unsw.edu.au
Mon Jan 10 21:49:32 CET 2011

On 10/01/2011, at 13:27, Simon Marlow wrote:

> On 10/01/2011 13:02, Max Bolingbroke wrote:
>> However, I remember the last time this came up there were some issues
>> that might make migration painful. From the top of my head:
>> 1) Some people expressed concern that they would have to use two
>> revision control systems to work on GHC, because not all GHC
>> dependencies would be git-based.
> It would be a prerequisite to switching that a GHC developer only has to use one VCS.  So we either migrate dependencies to git, or mirror them in GHC-specific git branches.

I'm not sure how that is going to work. It might well be possible to build GHC using only git. But most GHC developers also contribute to various libraries which are often quite intimately linked to GHC. In particular, GHC patches are often accompanied by library patches. Unless all those libraries switch to git, too, we'll have to use both git and darcs which would be *really* annoying.

Personally, I rather dislike git, mostly for the reasons that Malcolm already mentioned. Compared to darcs, it seems to get in the way much too often. It also seems to make finding buggy patches rather hard. But maybe I just don't know how to use it properly. In any case, a switch to git wouldn't deter me from contributing to GHC, but neither would a switch to any other VCS. I would certainly swear more often while developing, though.


More information about the Glasgow-haskell-users mailing list