Eric Kow <[email protected]> writes: > Now that we have solved the immediate problem, how do we convince > ourselves that this is *only* a darcs obliterate -O problem and not > something deeper? I don't see why it could be anything deeper. The code in obliterate -O is clearly broken, as it builds the context out of the *matched* patch sequence.
You could maybe argue that this is due to missing functionality in libdarcs to safely build contexts (I have made a step in that direction, but it is not enforcing that the context is correct with regards to the repository, just with regards to listing direction). Or you could argue that it is an extra functionality in libdarcs that it allows to build contexts unsafely. You could also argue that darcs is fragile because a bad context can throw it off quite badly. On the other hand, this is wired into darcs on a very deep level. We do protect contexts by a hash, which could be maybe made mandatory, to keep people from forging contexts. The balance between usability and safety is, as usual, hard to find. Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
