Chris Rorvick <[email protected]> writes:
> Had I written the the "already exists" advice in the context of these
> additional statuses I would have said "the destination *tag* reference
> already exists", or maybe even just "the destination *tag* already
> exists".
Yeah, now we do not use "already exists" for anything other than
refs/tags/, right? Your rewording sounds like the right thing to
make it even clearer.
Thanks for bringing it up.
Would it be sufficient to do this? I think "the tag already exists
in the remote" is already clear that we are talking about the
destination.
diff --git a/builtin/push.c b/builtin/push.c
index a2b3fbe..78789be 100644
--- a/builtin/push.c
+++ b/builtin/push.c
@@ -228,7 +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"
+ N_("Updates were rejected because the tag already exists\n"
"in the remote.");
static const char message_advice_ref_needs_force[] =
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
