While running the git-p4 tests, I noticed that t9814 has started
failing due to the (very ingenious!) chain-lint detection introduced
in:
bb79af9 t/test-lib: introduce --chain-lint option
I think that what's going on is that the chain-lint test is
getting itself confused by this test, which is designed to always
succeed, regardless of whether the individual sub-commands succeed
or not, since it's just setting up a pre-requisite for later use.
I've added an additional set of braces, which makes it clearer
to the --chain-lint code what's going on, but I'd be interested to
know if this is the right way to fix this.
Thanks,
Luke
Luke Diamand (1):
git-p4: prevent --chain-lint failure
t/t9814-git-p4-rename.sh | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
--
2.3.4.48.g223ab37