From: Federico Mena Quintero <federico@novell.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 4/4] Make git-pull complain and give advice when there is nothing to pull from
Date: Tue, 02 Oct 2007 18:36:30 -0500 [thread overview]
Message-ID: <1191368190.3776.206.camel@cacharro.xalalinux.org> (raw)
In-Reply-To: <1191367817.3776.192.camel@cacharro.xalalinux.org>
Signed-off-by: Federico Mena Quintero <federico@gnu.org>
---
git-pull.sh | 22 ++++++++++++++++++----
1 files changed, 18 insertions(+), 4 deletions(-)
diff --git a/git-pull.sh b/git-pull.sh
index c3f05f5..74bfc16 100755
--- a/git-pull.sh
+++ b/git-pull.sh
@@ -97,10 +97,24 @@ case "$merge_head" in
esac
curr_branch=${curr_branch#refs/heads/}
- echo >&2 "Warning: No merge candidate found because value of config option
- \"branch.${curr_branch}.merge\" does not match any remote branch fetched."
- echo >&2 "No changes."
- exit 0
+ echo >&2 "You asked me to pull without telling me which branch you"
+ echo >&2 "want to merge with, and 'branch.${curr_branch}.merge' in"
+ echo >&2 "your configuration file does not tell me either. Please"
+ echo >&2 "name which branch you want to merge on the command line and"
+ echo >&2 "try again (e.g. 'git pull <repository> <refspec>')."
+ echo >&2 "See git-pull(1) for details on the refspec."
+ echo >&2
+ echo >&2 "If you often merge with the same branch, you may want to"
+ echo >&2 "configure the following variables in your configuration"
+ echo >&2 "file:"
+ echo >&2
+ echo >&2 " branch.${curr_branch}.remote = <nickname>"
+ echo >&2 " branch.${curr_branch}.merge = <remote-ref>"
+ echo >&2 " remote.<nickname>.url = <url>"
+ echo >&2 " remote.<nickname>.fetch = <refspec>"
+ echo >&2
+ echo >&2 "See git-config(1) for details."
+ exit 1
;;
?*' '?*)
if test -z "$orig_head"
--
1.5.2.4
next prev parent reply other threads:[~2007-10-02 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 1:04 [PATCH 0/4] Make the documentation consistent for --track and --notrack Federico Mena Quintero
2007-09-18 1:07 ` [PATCH 1/4] Mention that git-branch will not automatically check out the new branch Federico Mena Quintero
2007-09-18 1:10 ` [PATCH 2/4] Copy the docs for --track and --notrack from git-checkout to git-branch Federico Mena Quintero
2007-09-18 1:11 ` [PATCH 3/4] Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docs Federico Mena Quintero
2007-09-18 22:38 ` Junio C Hamano
2007-10-02 23:30 ` [PATCH 0/4] Another round of the --track patches Federico Mena Quintero
2007-10-02 23:32 ` [PATCH 1/4] Say when --track is useful in the git-checkout docs Federico Mena Quintero
2007-10-02 23:33 ` [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs Federico Mena Quintero
2007-10-02 23:35 ` Federico Mena Quintero
2007-10-02 23:34 ` [PATCH 3/4] Note that git-branch will not automatically checkout the new branch Federico Mena Quintero
2007-10-02 23:36 ` Federico Mena Quintero [this message]
2007-09-18 1:12 ` [PATCH 4/4] Make git-pull give hints on what to do when there is no branch to merge from Federico Mena Quintero
2007-09-18 23:00 ` 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=1191368190.3776.206.camel@cacharro.xalalinux.org \
--to=federico@novell.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).