I confirmed this bug is still there in 1.0.3. However, I got the error earlier today myself with 1.0.1, and then upgraded to 1.0.3 and got "No conflicts to resolve!" instead. So something has improved here, but it's not fixed completely. (I must have had a different variation). Mark
_______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
