On Thu, Aug 09, 2007 at 12:40:37PM +0200, Tommy Pettersson wrote: > On Wed, Aug 08, 2007 at 01:22:50PM -0700, David Roundy wrote: > > On Wed, Aug 08, 2007 at 09:43:03PM +0200, Eric Y. Kow wrote: > > > On Tue, Aug 07, 2007 at 18:08:01 -0700, David Roundy wrote: > > > > Here's a fix for the trouble we've had with optimize --reorder when > > > > executed on the latest darcs unstable repository. > > > > > > I haven't looked yet, but it may be worth re-sending to or rebasing on > > > stable. > > > > I suspect this round of stable is going to have to take a while to let > > things stabilize, so I'll wait until Tommy asks. The patch that fixes > > (well, reduces) the performance regression in optimize will also have the > > effect of hiding this bug, so that might be a better choice between the > > two. > > The 'optimize optimize' patch applies nicely to darcs-stable, > and seems to fix (or hide) the bug, so I'm satisfied with that > one.
Good. > Acidently I ran into another problem: bug in get_extra commuting > patch, when I try to pull from latest unstable to stable (with > "all" darcs versions). I guess this is the long-standing > hard-to-fix merger bug that will disappear with the change to > cancellation patches? I'm working around it by pulling patches > via temporary repos to avoid the failing merger commutation. Argh! :( -- David Roundy Department of Physics Oregon State University _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
