Old darcs 1.0.9 I think. I am reluctant to switch to darcs 2.0 until I am confident that it works right, and without the major slow-downs that Simon reports.
If this is simply a known bug in 1.0.9 we can, I believe, work around it by shipping a tar-ball of a recent repo. I was puzzled because I didn't think there was a show-stopping bug like this in 1.0.9 in a repo that has no conflicts. Simon | -----Original Message----- | From: Eric Kow [mailto:[EMAIL PROTECTED] | Sent: 02 May 2008 10:08 | To: [EMAIL PROTECTED]; [email protected]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; | [EMAIL PROTECTED]; [EMAIL PROTECTED]; Simon Peyton-Jones | Subject: [issue829] pull => bug in get_extra commuting patch | | | | Simon/Norman: what version of darcs was this? I'm hoping this is something that | darcs2 has already fixed. | | More specifically, looking at issue279, I understand that David has fixed a | get_extra commuting patch bug between darcses 1.0.9 and 2.0.0. | | ---------- | nosy: +kowey | priority: -> bug | status: unread -> chatting | title: trouble getting repo up to date -> pull => bug in get_extra commuting patch | | __________________________________ | Darcs bug tracker <[EMAIL PROTECTED]> | <http://bugs.darcs.net/issue829> | __________________________________
_______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
