git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 4/4] Make git-pull complain and give advice when there is nothing to pull from

From
FQFederico Mena Quintero <federico@novell.com>
Date
Oct 2, 2007, 23:36 UTC
Message-ID
<1191368190.3776.206.camel@cacharro.xalalinux.org>
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
Previous: Federico Mena QuinteroNext: Federico Mena Quintero
Message 11 of 13 in “Make the documentation consistent for --track and --notrack”
  1. 0/4 Make the documentation consistent for --track and --notrackFederico Mena Quintero, Sep 18, 2007
  2. 1/4 Mention that git-branch will not automatically check out the new branchFederico Mena Quintero, Sep 18, 2007
  3. 2/4 Copy the docs for --track and --notrack from git-checkout to git-branchFederico Mena Quintero, Sep 18, 2007
  4. 3/4 Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docsFederico Mena Quintero, Sep 18, 2007
  5. Junio C HamanoSep 18, 2007
  6. 0/4 Another round of the --track patchesFederico Mena Quintero, Oct 2, 2007
  7. 1/4 Say when --track is useful in the git-checkout docs.Federico Mena Quintero, Oct 2, 2007
  8. 1/4 Add documentation for --track and --no-track to the git-branch docs.Federico Mena Quintero, Oct 2, 2007
  9. Federico Mena QuinteroOct 2, 2007
  10. 3/4 Note that git-branch will not automatically checkout the new branchFederico Mena Quintero, Oct 2, 2007
  11. 4/4 Make git-pull complain and give advice when there is nothing to pull fromFederico Mena Quintero, Oct 2, 2007
  12. 4/4 Make git-pull give hints on what to do when there is no branch to merge fromFederico Mena Quintero, Sep 18, 2007
  13. Junio C HamanoSep 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.