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>
Junio C Hamano committed
Jan 24, 2013 at 21:09 UTC
b4cf8db27502f613fcff3fd871c8e31d23f49c7d
1 file changed
+1
-2
builtin/push.c
+1
-2
@@ -228,8 +228,7 @@ static const char message_advice_ref_fetch_first[] =
228
"See the 'Note about fast-forwards' in 'git push --help' for details.");
229
230
static const char message_advice_ref_already_exists[] =
231
- N_("Updates were rejected because the destination reference already exists\n"
232
- "in the remote.");
231
+ N_("Updates were rejected because the tag already exists in the remote.");
232
233
static const char message_advice_ref_needs_force[] =
234
N_("You cannot update a remote ref that points at a non-commit object,\n"