tests-subrepo-git: emit a different "pwned" message based on the test
Having a single "pwned" message which may or may not be emitted during the
tests for CVE-2016-3068 leads to extra confusion. Allow each test to emit
a more detailed message based on what the expectations are.
In both cases, we expect a version of git which has had the vulnerability
plugged, as well as a version of mercurial which also knows about
GIT_ALLOW_PROTOCOL. For the first test, we make sure GIT_ALLOW_PROTOCOL is
unset, meaning that the ext-protocol subrepo should be ignored; if it
isn't, there's either a problem with mercurial or the installed copy of
git.
For the second test, we explicitly allow ext-protocol subrepos, which means
that the subrepo will be accessed and a message emitted confirming that
this was, in fact, our intention.
#require test-repo
$ cd "`dirname "$TESTDIR"`"
look for python scripts that do not use /usr/bin/env
$ hg files 'set:grep(r"^#!.*?python") and not grep(r"^#!/usr/bin/env python")'
[1]
look for shell scripts that do not use /bin/sh
$ hg files 'set:grep(r"^#!.*/bin/sh") and not grep(r"^#!/bin/sh")'
[1]