Tommy Pettersson <[EMAIL PROTECTED]> added the comment: On Sat, Jan 12, 2008 at 10:00:10PM -0000, Tommy Pettersson wrote: > An alternative is to switch to the current darcs-stable, which I
Darn, that is not true. The bug is actually a known bug. A backport exists (which is why I wrongly thought darcs-stable was ok, but I haven't pushed it yet). The reason I haven't pushed the backport is (beside I wasn't aware it could be triggered this way) it conflicts badly with darcs-unstable, and the required conflict resolution is of course even worse. I think I'm ready to wrap up a release of 1.1.0 tomorrow (well rc1, and make it final within a week), but I'm not sure that's a good idea when everything is focused on darcs2. Anyway, with the inclusion of this unpushed backported fix I think 1.1.0 is really very stable. I've almost only pushed fixes and trivial stuff of the darcs guts to it (and some incomplete hashed-format stuff due to dependencies). It's the UI that has the most changes. On the other hand, darcs2 has the new GADT testing and better unit testing, so darcs2 might already be even more safe with the old repo format than darcs1, even without real world testing. By looking at the reported bugs it has mostly been optimization issues. __________________________________ Darcs bug tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue573> __________________________________ _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
