Generic deriving in GHC

[Simon Peyton-Jones]

If you want to get fast access via darcs again, here's the workflow:


·         Start with your local repo ghc-generic-11Oct10; call it $(OLD)

·         Ask me to create a new repo on darcs.haskell.org, a clone of HEAD (say ghc-generic-28Jan11)

·         darcs get that repo; call that local rep $(NEW)

·         pull every patch from $(NEW) into $(OLD)

·         resolve all conflicts. Now $(OLD) has a tree up to date wrt $(NEW), but also containing all your modifications

·         Now the big step: cp -r $(OLD)/compiler $(NEW)/compiler

This simply overwrites $(NEW) with the files

·         Record one giant patch in $(NEW)

·         Push to the server

Now you have a new repo, up to date wrt HEAD, and one giant patch of your changes.  You can pull into it from HEAD until it starts getting slow again, and then repeat.

The difficulty of working with long-lived branches is the main reason we're planning the move to Git.

Simon

From: José Pedro Magalhães [mailto:jpm at cs.uu.nl]
Sent: 28 January 2011 13:12
To: Max Bolingbroke
Cc: Simon Peyton-Jones; cvs-ghc at haskell.org
Subject: Re: Generic deriving in GHC


2011/1/28 Max Bolingbroke <batterseapower at hotmail.com<mailto:batterseapower at hotmail.com>>
2011/1/28 José Pedro Magalhães <jpm at cs.uu.nl<mailto:jpm at cs.uu.nl>>:
>> darcs get http://darcs.haskell.org/ghc-generic-11Oct10/ghc --lazy
>> cd ghc
>> darcs pull http://darcs.haskell.org/ghc -a
>
> and see if darcs hangs on this last step?
It does not hang for me (Darcs 2.4.4). It does take a few minutes though!

Interesting. After about an hour it indeed terminates, in my case with a few conflicts.

Amazing how it can stay doing whatever it is doing without giving any user feedback for an hour.


Thanks,
Pedro


Cheers,
Max

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cvs-ghc/attachments/20110128/9be9130b/attachment-0001.htm>