But rather than searching for this specific string to be there I would be looking for /\br=\w+/ not being there. You can use whatever string to indicate that the patch isn’t reviewed but a reviewed patch will always have “r=something” in the commit string.

[That was intentional, because sometimes I'll want to commit with something like "Fix typo to kick tinderboxen into doing another build" as the description (or some other such thing without adding a r= somewhere). Also, Mozilla's style of indicating reviews probably doesn't extend to other open source projects that use Mercurial (or, for that matter, personal on-disk repositories).]

Secondly for a “buggy patch” pre-hook thats both hard and easy.

Just cause it to build both debug and release Firefox, run full set of tests [to see if they pass], then check if any other commits happend since then, [re-]merge and push! Probably not useful, due to turn-around-time though

[I expect people interested in using this could make any necessary changes, and to be frank, I don't care much about Windows here because I don't use it (for pushes, or for much of anything else, to be honest). That said, when I installed the build toolchain on Windows a few days ago, the start-* scripts were spawning a bash shell, and the Mercurial there was responding to an hgrc in ~/.hgrc, so I'm not so sure this doesn't work there.

"Buggy patch" was a joke about a hook that would be intelligent enough to find any bug, not just ones that would show up in automated testing runs — solving-the-halting-problem sort of bugs, that is.]