Eric Kow <[email protected]> writes: >> If I >> were heavily editing them all the time it might make sense to have a >> whitelist feature like Florent suggested, or to change up the definition >> of is_malicious_path like I suggested. > > It may be worth thinking about making the --dont-restrict-paths option a > bit more conservative, so that instead of not restricting paths, it only > restricts them minimally (i.e. it tightens the definition of > is_malicious_path). > I beg to differ: there's one thing worse than flag proliferation, it's byzantine flags. If you start going that road, someone will require some other level of tightness, and there will be no end. Having only all checks on or all cares off means than once you've removed the net, you're on your own, which is a good thing. We want flags to be as orthogonal as possible.
Florent _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
