From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Make git-{pull,rebase} no-tracking message friendlier
Date: Mon, 27 Feb 2012 23:06:31 +0100 [thread overview]
Message-ID: <vpq399wc4ns.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1330013115-26355-1-git-send-email-cmn@elego.de> ("Carlos Martín Nieto"'s message of "Thu, 23 Feb 2012 17:05:15 +0100")
Carlos Martín Nieto <cmn@elego.de> writes:
> - echo "You asked me to $cmd without telling me which branch you
> -want to $op_type $op_prep, and 'branch.${branch_name#refs/heads/}.merge' in
> -your configuration file does not tell me, either. Please
> -specify which branch you want to use on the command line and
> + echo "You asked me to $cmd without telling me which branch you want to
> +$op_type $op_prep, and there is no tracking information for the current branch.
> +Please specify which branch you want to use on the command line and
> try again (e.g. '$example').
At this point, it may be better to actually give the full command
instead of just this "(e.g. '$example')", i.e. stg like
git $op_type <remote> $example
I also saw users confused by the message (indeed without reading it,
but ...). Giving them something as close as possible to
cut-and-paste-able command should help.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-02-27 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 16:05 [RFC/PATCH] Make git-{pull,rebase} no-tracking message friendlier Carlos Martín Nieto
2012-02-23 20:28 ` Junio C Hamano
2012-02-27 17:07 ` Carlos Martín Nieto
2012-02-27 22:06 ` Matthieu Moy [this message]
2012-02-29 3:57 ` Carlos Martín Nieto
2012-02-29 8:09 ` Matthieu Moy
2012-02-29 17:34 ` Carlos Martín Nieto
2012-02-29 18:41 ` [PATCH] Make git-{pull,rebase} message without tracking information friendlier Carlos Martín Nieto
2012-02-29 20:14 ` Junio C Hamano
2012-03-04 4:41 ` Carlos Martín Nieto
2012-03-05 7:49 ` Junio C Hamano
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=vpq399wc4ns.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
/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).