From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: [PATCH] push: error out when the "upstream" semantics does not make sense
Date: Thu, 05 Apr 2012 12:48:58 -0700 [thread overview]
Message-ID: <7vlima5591.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120405184345.GA6448@burratino> (Jonathan Nieder's message of "Thu, 5 Apr 2012 13:43:45 -0500")
Jonathan Nieder <jrnieder@gmail.com> writes:
> I worry that a beginner seeing this message would think it means that
> when "master" is set up to track origin/master that there is no way to
> push that branch to any other repository.
>
> Maybe something like
>
> die(_(
> "You are pushing to remote '%s', which is not the upstream of your\n"
> "current branch '%s', without specifying a refspec.\n"),
> remote->name, branch->name);
>
> would be harder to misunderstand.
Perhaps. Do we need to rephrase it without using the word 'refspec'
(e.g. "without telling me what to push"), or there is no point avoiding
jargon because other jargons (i.e. 'remote' and 'upstream') already appear
in the sentence?
next prev parent reply other threads:[~2012-04-05 19:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 23:26 What's cooking in git.git (Apr 2012, #02; Wed, 4) Junio C Hamano
2012-04-05 12:47 ` Jeff King
2012-04-05 16:00 ` [PATCH] push: error out when the "upstream" semantics does not make sense Junio C Hamano
2012-04-05 18:43 ` Jonathan Nieder
2012-04-05 19:48 ` Junio C Hamano [this message]
2012-04-05 19:58 ` Jonathan Nieder
2012-04-05 20:01 ` Junio C Hamano
2012-04-05 20:23 ` Jonathan Nieder
2012-04-05 20:24 ` Matthieu Moy
2012-04-05 20:34 ` Junio C Hamano
2012-04-06 7:16 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vlima5591.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).