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
New submission from Trent Buck [EMAIL PROTECTED]:
[Apologies if this arrives twice; I'm having MUA problems.]
Darcs does not warn users when they attempt to remove a checkpoint
patch, and gives confusing/obtuse errors afterwards.
Below is a minimal transcript demonstrating the problem. First,
New submission from Zooko [EMAIL PROTECTED]:
This is interesting. On two different Windows computers of my own,
plus Arno's Windows computer, several different repos have turned out
to be inconsistent once we upgraded to darcs v1.0.9.
Is there any known issue that would cause this? I
