Hi Tommy, > Sun Aug 19 17:34:15 CEST 2007 Tommy Pettersson <[EMAIL PROTECTED]> > * backport David's optimize --reorder bugfix to stable [issue494] > > Sun Aug 19 17:39:05 CEST 2007 Tommy Pettersson <[EMAIL PROTECTED]> > * resolv conflicts (issue494) > 1) fix bug that revealed itself in optimize --reorder on unstable repo > 2) backport David's optimize --reorder bugfix to stable [issue494]
I hope I'm not holding you up. I'm going to hang on to this until you tell me we don't really have any other choice. If you tell me that I should go ahead and apply this, I will asap. Otherwise, one option might be to introduce some temporary version of the code, say, prefixed with the name issue494 and appended to the end of the relevant files where they are not likely to cause conflicts. I can then apply these patches, resolve the less hairy conflicts and then delete the functions. Do you think that might work, or would it just make things really bad for stable? Also, I haven't yet done the research into your questions. I think there might be some threads of the mailing list where I asked questions about the functions like sort_coalesce, etc if it helps. -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français.
pgpoHM14KHvoq.pgp
Description: PGP signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
