From: Brandon Casey <drafnel@gmail.com>
To: git@vger.kernel.org
Cc: artem.bityutskiy@linux.intel.com, Brandon Casey <drafnel@gmail.com>
Subject: [PATCH 2/2] builtin/apply.c: report error on failure to recognize input
Date: Sat, 3 Dec 2011 14:35:50 -0600 [thread overview]
Message-ID: <1322944550-27344-2-git-send-email-drafnel@gmail.com> (raw)
In-Reply-To: <1322944550-27344-1-git-send-email-drafnel@gmail.com>
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>
---
Initially, I was reluctant to change the error message, thinking that
error messages for plumbing commands were not supposed to change. But I
think I was wrong in that thought, so I changed the error message so it
was a more descriptive "unrecognized input".
-Brandon
builtin/apply.c | 10 +++++-----
t/t4136-apply-check.sh | 19 +++++++++++++++++++
2 files changed, 24 insertions(+), 5 deletions(-)
create mode 100755 t/t4136-apply-check.sh
diff --git a/builtin/apply.c b/builtin/apply.c
index 84a8a0b..46dcf3c 100644
--- a/builtin/apply.c
+++ b/builtin/apply.c
@@ -3590,15 +3590,12 @@ static int write_out_one_reject(struct patch *patch)
return -1;
}
-static int write_out_results(struct patch *list, int skipped_patch)
+static int write_out_results(struct patch *list)
{
int phase;
int errs = 0;
struct patch *l;
- if (!list && !skipped_patch)
- return error("No changes");
-
for (phase = 0; phase < 2; phase++) {
l = list;
while (l) {
@@ -3724,6 +3721,9 @@ static int apply_patch(int fd, const char *filename, int options)
offset += nr;
}
+ if (!list && !skipped_patch)
+ die("unrecognized input");
+
if (whitespace_error && (ws_error_action == die_on_ws_error))
apply = 0;
@@ -3741,7 +3741,7 @@ static int apply_patch(int fd, const char *filename, int options)
!apply_with_reject)
exit(1);
- if (apply && write_out_results(list, skipped_patch))
+ if (apply && write_out_results(list))
exit(1);
if (fake_ancestor)
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
--
1.7.8
next prev parent reply other threads:[~2011-12-03 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 20:35 [PATCH 1/2] t/t4131-apply-fake-ancestor.sh: fix broken test Brandon Casey
2011-12-03 20:35 ` Brandon Casey [this message]
2011-12-04 13:30 ` [PATCH 2/2] builtin/apply.c: report error on failure to recognize input Artem Bityutskiy
2011-12-04 15:39 ` Brandon Casey
2011-12-05 19:27 ` Junio C Hamano
2011-12-05 22:38 ` Brandon Casey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1322944550-27344-2-git-send-email-drafnel@gmail.com \
--to=drafnel@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).