# HG changeset patch
# User Martin von Zweigbergk <martinvonz@google.com>
# Date 1418926298 28800
# Node ID 80a37f706011146973a1443d2351d4b3fbf83bbb
# Parent  cb9d845406e5b97e6fed70bab654e71f7083f82c
test-check-commit-hg: clarify misleading "commit message rules" error

The test case doesn't only check the commit message, but also the
patch, which can result in confusing output like

  +  Revision df6f06d17100 does not comply to commit message rules
  +  ------------------------------------------------------
  +  32: adds double empty line
  +
  +

even when there are no double blank lines in the commit message. Drop
the "commit message" part to make it less confusing.

diff -r cb9d845406e5 -r 80a37f706011 tests/test-check-commit-hg.t
--- a/tests/test-check-commit-hg.t	Sun Dec 21 13:02:59 2014 +0000
+++ b/tests/test-check-commit-hg.t	Thu Dec 18 10:11:38 2014 -0800
@@ -14,7 +14,7 @@
   $ for node in `hg log --rev 'draft() and ::.' --template '{node|short}\n'`; do
   >    hg export $node | contrib/check-commit > ${TESTTMP}/check-commit.out
   >    if [ $? -ne 0 ]; then
-  >        echo "Revision $node does not comply to commit message rules"
+  >        echo "Revision $node does not comply to rules"
   >        echo '------------------------------------------------------'
   >        cat ${TESTTMP}/check-commit.out
   >        echo