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 <gitster@pobox.com>

diff --git a/builtin/push.c b/builtin/push.c
index a2b3fbed6a4be128bbfc2c3f7c3b278a91680f80..3963fbb01466d44e5e9a99e34622fc1a01987dfe 100644 (file)
--- 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"