aboutsummaryrefslogtreecommitdiff
path: root/builtin
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-04-15 04:36:25 -0500
committerJunio C Hamano <gitster@pobox.com>2010-04-17 12:40:19 -0700
commita6ccbbdb66be4e4b90bd54fc644d6366491996b5 (patch)
tree0fa084b65ce210b4edfbaadd94b7a90f412ab8c5 /builtin
parent3e8c0eb48f25de62d6f48168487180363fa86cfb (diff)
downloadgit-a6ccbbdb66be4e4b90bd54fc644d6366491996b5.tar.gz
git-a6ccbbdb66be4e4b90bd54fc644d6366491996b5.tar.xz
tag -v: use RUN_GIT_CMD to run verify-tag
This is the preferred way to run a git command. The only obvious observable effects I can think of are that the exec is properly reported in GIT_TRACE output and that verifying signed tags will still work if the git-verify-tag hard link in gitexecdir goes missing. Helped-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin')
-rw-r--r--builtin/tag.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/builtin/tag.c b/builtin/tag.c
index 4ef1c4f50..d311491e4 100644
--- a/builtin/tag.c
+++ b/builtin/tag.c
@@ -147,11 +147,11 @@ static int delete_tag(const char *name, const char *ref,
static int verify_tag(const char *name, const char *ref,
const unsigned char *sha1)
{
- const char *argv_verify_tag[] = {"git-verify-tag",
+ const char *argv_verify_tag[] = {"verify-tag",
"-v", "SHA1_HEX", NULL};
argv_verify_tag[2] = sha1_to_hex(sha1);
- if (run_command_v_opt(argv_verify_tag, 0))
+ if (run_command_v_opt(argv_verify_tag, RUN_GIT_CMD))
return error("could not verify the tag '%s'", name);
return 0;
}