RFC: migrating to git

[Simon Marlow]

On 17/01/2011 14:08, rl at cse.unsw.EDU.AU wrote:
> On Mon, January 17, 2011 11:08 pm, Simon Marlow wrote:
>>
>> So, we've decided to try switching to git.
>
> That's very sad!
>
>> The changeover will be
>> staged: first we'll switch the GHC repository, and if all goes well
>> we'll switch the libraries and other sub-repositories.  This means we can
>> experiment with git for the GHC repo while we establish exactly what
>> strategy to use for each sub-repository (change the master to git, or
>> leave the master in darcs and mirror).  It does mean for a short while GHC
>> developers will have to use two VCS tools, but the sync-all tool will hide
>> the difference to some extent.
>>
>> The next step is to set up the git repo, probably based on the mirror I
>> set up last week, and sort out various details (commit emails, buildbots,
>> wiki updates etc.).  I'll send out a notification once things are set up
>> and we have a date/time for the git repo going live.
>
> Would it be possible to also produce a definite timeline for when the
> other repos will switch to git? Having to work with two different VCS in
> one project is a bit above my pain threshold so I'd like to know when I'll
> be able to get back into action after the switch.

Absolutely.  The reason I didn't give a definite timescale yet is that 
we're currently finalizing our future release plans and the two are 
connected, because we want to minimize the amount of merging we have to 
do between a git branch and a darcs branch.  Anyway, I don't expect the 
multi-VCS situation will persist for more than a month or so, and 
certainly not across a release.

Cheers,
	Simon