From: "Carlos Martín Nieto" <cmn@elego.de>
To: git@vger.kernel.org
Subject: [RFC/PATCH] Make git-{pull,rebase} no-tracking message friendlier
Date: Thu, 23 Feb 2012 17:05:15 +0100 [thread overview]
Message-ID: <1330013115-26355-1-git-send-email-cmn@elego.de> (raw)
The current message is too long and at too low a level for anybody to
understand it if they don't know about the configuration format
already.
Reformat it to show the commands a user would be expected to use,
instead of the contents of the configuration file.
---
As annoying as it is when people simply paste the output of 'git pull'
and ask "what does it mean" without even reading it, I have to admit
that as a new user, I'd also be scared off by this message. Using
git-remote and git-branch should make it less scary and more relatable
for the user. I'm not aware of a way to set branch.$branch.rebase with
porcelain, so I put in a config command there. Better
solutions/wordings welcome; I'd really like to get rid of the old
message.
git-parse-remote.sh | 23 ++++++++---------------
1 files changed, 8 insertions(+), 15 deletions(-)
diff --git a/git-parse-remote.sh b/git-parse-remote.sh
index b24119d..96e76a9 100644
--- a/git-parse-remote.sh
+++ b/git-parse-remote.sh
@@ -65,26 +65,19 @@ Please specify which branch you want to $op_type $op_prep on the command
line and try again (e.g. '$example').
See git-${cmd}(1) for details."
else
- 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').
See git-${cmd}(1) for details.
If you often $op_type $op_prep the same branch, you may want to
-use something like the following in your configuration file:
- [branch \"${branch_name#refs/heads/}\"]
- remote = <nickname>
- merge = <remote-ref>"
- test rebase = "$op_type" &&
- echo " rebase = true"
- echo "
- [remote \"<nickname>\"]
- url = <url>
- fetch = <refspec>
+run something like:
-See git-config(1) for details."
+ git remote add <remote> <url>
+ git branch --set-upstream ${branch_name#refs/heads/} <remote>/<remote-branch>"
+ test rebase = "$op_type" &&
+ echo " git config branch.${branch_name#refs/heads/}.rebase true"
fi
exit 1
}
--
1.7.8.352.g876a6f
next reply other threads:[~2012-02-23 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 16:05 Carlos Martín Nieto [this message]
2012-02-23 20:28 ` [RFC/PATCH] Make git-{pull,rebase} no-tracking message friendlier Junio C Hamano
2012-02-27 17:07 ` Carlos Martín Nieto
2012-02-27 22:06 ` Matthieu Moy
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=1330013115-26355-1-git-send-email-cmn@elego.de \
--to=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).