Quite straightforward.  Going in.

> Here's a patch to make optimize --reorder faster much faster,
> by reversing a performance regression that I introduced earlier.

For the interested:

The optimize works by removing all patches (since the last checkpoint?),
magically reordering them, and then adding them back in the new order.
Before, we would update the pristine cache along the way, both in
removing the patches, and in adding them back in (add a patch, update
pristine, add a patch, ...).  This is silly because optimize should not
have any net effect on pristine anyway.  Thus the optimisation consists
in _not_ performing the pristine cache updates.

-- 
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon français.

Attachment: pgpKDOg5SoNmd.pgp
Description: PGP signature

_______________________________________________
darcs-devel mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-devel

Reply via email to