DPH & vector

[Simon Peyton-Jones]

Roman

OK, thanks.  But the questions are:

| (1) how far you got the with the integration and when you expect to push
| the patches and
| (2) whether we can help in any way.

We make a release candidate end of next week, and we don't want to have pushed a big patch hours before that.

Simon

| -----Original Message-----
| From: Leshchinskiy, Roman [mailto:Roman.Leshchinskiy at sc.com]
| Sent: 15 September 2010 09:55
| To: Manuel M T Chakravarty; Roman Leshchinskiy
| Cc: Simon Peyton-Jones; Ben Lippmeier
| Subject: RE: DPH & vector
| 
| The problem is that the changes I made to vector for DPH support
| actually break some vectorish things. This means that I can't push those
| patches to vector yet unless I want to be lynched by vector users. I
| really hope to sort this out this weekend.
| 
| The main thing we have to get into the tree is the vector tarball but
| that isn't possible until I push the patches.
| 
| Roman
| 
| -----Original Message-----
| From: Manuel M T Chakravarty [mailto:chak at cse.unsw.edu.au]
| Sent: Tuesday, September 14, 2010 12:38 PM
| To: Roman Leshchinskiy; Leshchinskiy, Roman
| Cc: Simon Peyton-Jones; Ben Lippmeier
| Subject: DPH & vector
| 
| Hi Roman,
| 
| We just had out weekly Skype call and so were wondering how you are
| going with integrating vector into DPH.  I told Simon about your
| problems with Internet access outside of work and we were worried that
| this may prevent you from completing and pushing the changes.  In
| particular, Simon just pushed the new type checker, so you will need to
| get a lot of patches, not just push yours.
| 
| As you know, GHC HQ wants to put out a release candidate in about a week
| and it would put us into a bad position if that doesn't include the
| vector-based DPH packages as we lose the ability to moves patches
| between the release branch and the HEAD if there are major changes after
| the branch.
| 
| So, we were wondering
| 
| (1) how far you got the with the integration and when you expect to push
| the patches and
| (2) whether we can help in any way.
| 
| For example, if it helps, you can just email your patches to me and I
| integrate them into the latest tree (including Simon's changes).
| 
| If the integration isn't perfect, we still need to get it into the tree
| (and add the necessary fixes when they are ready).
| 
| If you are held up by the fact that you didn't talk to Ian yet about how
| to handle the dependency on vector, then just send the patches to me and
| I will take care of that.  In any case, we are running out of time!
| 
| Cheers,
| Manuel
| 
| This email and any attachments are confidential and may also be privileged.
| If you are not the addressee, do not disclose, copy, circulate or in any
| other way use or rely on the information contained in this email or any
| attachments.  If received in error, notify the sender immediately and delete
| this email and any attachments from your system.  Emails cannot be guaranteed
| to be secure or error free as the message and any attachments could be
| intercepted, corrupted, lost, delayed, incomplete or amended.  Standard
| Chartered PLC and its subsidiaries do not accept liability for damage caused
| by this email or any attachments and may monitor email traffic.
| 
| 
| 
| Standard Chartered PLC is incorporated in England with limited liability
| under company number 966425 and has its registered office at 1 Aldermanbury
| Square, London, EC2V 7SB.
| 
| 
| 
| Standard Chartered Bank ("SCB") is incorporated in England with limited
| liability by Royal Charter 1853, under reference ZC18.  The Principal Office
| of SCB is situated in England at 1 Aldermanbury Square, London EC2V 7SB. In
| the United Kingdom, SCB is authorised and regulated by the Financial Services
| Authority under FSA register number 114276.
| 
| 
| 
| If you are receiving this email from SCB outside the UK, please click
| http://www.standardchartered.com/global/email_disclaimer.html to refer to the
| information on other jurisdictions.
| 
|