From b4cf8db27502f613fcff3fd871c8e31d23f49c7d Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Thu, 24 Jan 2013 21:09:00 -0800 Subject: [PATCH] push: finishing touches to explain REJECT_ALREADY_EXISTS better Now that "already exists" errors are given only when a push tries to update an existing ref in refs/tags/ hierarchy, we can say "the tag", instead of "the destination reference", and that is far easier to understand. Pointed out by Chris Rorvick. Signed-off-by: Junio C Hamano --- builtin/push.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/builtin/push.c b/builtin/push.c index a2b3fbed6..3963fbb01 100644 --- a/builtin/push.c +++ b/builtin/push.c @@ -228,8 +228,7 @@ static const char message_advice_ref_fetch_first[] = "See the 'Note about fast-forwards' in 'git push --help' for details."); static const char message_advice_ref_already_exists[] = - N_("Updates were rejected because the destination reference already exists\n" - "in the remote."); + N_("Updates were rejected because the tag already exists in the remote."); static const char message_advice_ref_needs_force[] = N_("You cannot update a remote ref that points at a non-commit object,\n" -- 2.26.2