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

[PATCH 4/5] branch: mention start_name in set-upstream error messages

From
Jeff King <peff@peff.net>
Date
Apr 2, 2013, 19:04 UTC
Message-ID
<20130402190451.GD32316@sigill.intra.peff.net>
In-Reply-To
<20130402190134.GA17784@sigill.intra.peff.net>

If we refuse a branch operation because the tracking start_name the user gave us is bogus, we just print something like:

 fatal: Cannot setup tracking information; start point is not a branch

If we mention the actual name we tried to use, that may help the user figure out why it didn't work (e.g., if they gave us the arguments in the wrong order).

Signed-off-by: Jeff King <peff@peff.net>
---
 branch.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/branch.c b/branch.c
index 060e9e3..d6f4001 100644
--- a/branch.c
+++ b/branch.c
@@ -198,9 +198,9 @@ static const char upstream_missing[] =
 }
 
 static const char upstream_not_branch[] =
-N_("Cannot setup tracking information; starting point is not a branch.");
+N_("Cannot setup tracking information; starting point '%s' is not a branch.");
 static const char upstream_missing[] =
-N_("Cannot setup tracking information; starting point does not exist");
+N_("Cannot setup tracking information; starting point '%s' does not exist");
 
 void create_branch(const char *head,
 		   const char *name, const char *start_name,
@@ -231,7 +231,7 @@ void create_branch(const char *head,
 	real_ref = NULL;
 	if (get_sha1(start_name, sha1)) {
 		if (explicit_tracking)
-			die(_(upstream_missing));
+			die(_(upstream_missing), start_name);
 		die("Not a valid object name: '%s'.", start_name);
 	}
 
@@ -239,14 +239,14 @@ void create_branch(const char *head,
 	case 0:
 		/* Not branching from any existing branch */
 		if (explicit_tracking)
-			die(_(upstream_not_branch));
+			die(_(upstream_not_branch), start_name);
 		break;
 	case 1:
 		/* Unique completion -- good, only if it is a real branch */
 		if (prefixcmp(real_ref, "refs/heads/") &&
 		    prefixcmp(real_ref, "refs/remotes/")) {
 			if (explicit_tracking)
-				die(_(upstream_not_branch));
+				die(_(upstream_not_branch), start_name);
 			else
 				real_ref = NULL;
 		}
-- 
1.8.2.rc0.33.gd915649
Previous: Jeff KingNext: Garrett Cooper
Message 11 of 15 in “[BUG] inconsistent behavior with --set-upstream vs --set-upstream-to”
  1. Garrett CooperApr 2, 2013
  2. Jeff KingApr 2, 2013
  3. Garrett CooperApr 2, 2013
  4. Jeff KingApr 2, 2013
  5. 0/5 branch --set-upstream-to error-message improvementsJeff King, Apr 2, 2013
  6. 1/5 t3200: test --set-upstream-to with bogus refsJeff King, Apr 2, 2013
  7. 2/5 branch: factor out "upstream is not a branch" error messagesJeff King, Apr 2, 2013
  8. Garrett CooperApr 2, 2013
  9. Garrett CooperApr 2, 2013
  10. 3/5 branch: improve error message for missing --set-upstream-to refJeff King, Apr 2, 2013
  11. 4/5 branch: mention start_name in set-upstream error messagesJeff King, Apr 2, 2013
  12. Garrett CooperApr 2, 2013
  13. 5/5 branch: give advice when tracking start-point is missingJeff King, Apr 2, 2013
  14. Junio C HamanoApr 2, 2013
  15. Jonathan NiederApr 2, 2013

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.