summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorBrandon Casey <drafnel@gmail.com>2011-12-03 20:35:50 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-12-05 19:20:50 (GMT)
commitcc64b318f26c9e176c4f07b1a459a86e7a04c4eb (patch)
tree7199e2205d9d1ec141595731eec3a9c2388b3df1 /t
parent590a472b363ba9d6e75b1dbf07f20e80ae9a587d (diff)
downloadgit-cc64b318f26c9e176c4f07b1a459a86e7a04c4eb.zip
git-cc64b318f26c9e176c4f07b1a459a86e7a04c4eb.tar.gz
git-cc64b318f26c9e176c4f07b1a459a86e7a04c4eb.tar.bz2
builtin/apply.c: report error on failure to recognize input
When git apply is passed something that is not a patch, it does not produce an error message or exit with a non-zero status if it was not actually "applying" the patch i.e. --check or --numstat etc were supplied on the command line. Fix this by producing an error when apply fails to find any hunks whatsoever while parsing the patch. This will cause some of the output formats (--numstat, --diffstat, etc) to produce an error when they formerly would have reported zero changes and exited successfully. That seems like the correct behavior though. Failure to recognize the input as a patch should be an error. Plus, add a test. Reported-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Brandon Casey <drafnel@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
-rwxr-xr-xt/t4136-apply-check.sh19
1 files changed, 19 insertions, 0 deletions
diff --git a/t/t4136-apply-check.sh b/t/t4136-apply-check.sh
new file mode 100755
index 0000000..a321f7c
--- /dev/null
+++ b/t/t4136-apply-check.sh
@@ -0,0 +1,19 @@
+#!/bin/sh
+
+test_description='git apply should exit non-zero with unrecognized input.'
+
+. ./test-lib.sh
+
+test_expect_success 'setup' '
+ test_commit 1
+'
+
+test_expect_success 'apply --check exits non-zero with unrecognized input' '
+ test_must_fail git apply --check - <<-\EOF
+ I am not a patch
+ I look nothing like a patch
+ git apply must fail
+ EOF
+'
+
+test_done