From 367068e0dd1b7d6b5b4029749b326c6bad172498 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Thu, 24 Oct 2013 04:54:01 -0400 Subject: use parse_commit_or_die instead of custom message Many calls to parse_commit detect errors and die. In some cases, the custom error messages are more useful than what parse_commit_or_die could produce, because they give some context, like which ref the commit came from. Some, however, just say "invalid commit". Let's convert the latter to use parse_commit_or_die; its message is slightly more informative, and it makes the error more consistent throughout git. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano --- shallow.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'shallow.c') diff --git a/shallow.c b/shallow.c index 8a9c96d019..a273685e75 100644 --- a/shallow.c +++ b/shallow.c @@ -89,8 +89,7 @@ struct commit_list *get_shallow_commits(struct object_array *heads, int depth, cur_depth = *(int *)commit->util; } } - if (parse_commit(commit)) - die("invalid commit"); + parse_commit_or_die(commit); cur_depth++; if (cur_depth >= depth) { commit_list_insert(commit, &result); -- cgit v1.2.3