Hey,

Also, another patch which I would be interested in is one that adds
tests for the mechanism.  What tests exactly, I'm not entirely sure.
Some examples might be making sure that ignored files really are
ignored, that there aren't any weird interactions between boring
and ignored, that commands like pull and apply *still* affect
ignored files, etc.  Do think this would be a sensible step to take?

I've added a test suite and split up the patches as you
requested.  darcs pull and darcs apply still work on ignored
files.

I do agree with everyone else here that ignoring patches
would be a better solution.  But a working solution is better
than none at all.  I won't be offended if you replaced this
solution with a better one, in fact I'd be delighted.

Hoan

Attachment: CHANGESET
Description: Binary data

_______________________________________________
darcs-devel mailing list
[email protected]
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel

Reply via email to