Please review: #548 hg-active should catch mercurial.util.Abort Webrev: http://cr.opensolaris.org/~richlowe/onnv_548
Simple change, obvious results. I chose to only catch Abort, which mercurial tends to use to signal such errors, rather than a greater range of things which hg(1) would catch as, for our purposes, many of the others (EnvironmentError, for instance), are things for which I would prefer a backtrace. (in the context of webrev, and thus hg-active, I think most represent graver issues). Opinion welcome. I tested this in the obvious case via: hg-active -w . -p path/to/cadtest Which will abort as they are unrelated, and with this change output: Abort: repository is unrelated and exit indicating failure Thanks, -- Rich