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

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

From
Garrett Cooper <yaneurabeya@gmail.com>
Date
Apr 2, 2013, 19:39 UTC
Message-ID
<CAGHfRMA8oAX-vigeYXxEVzWsrcPaWw0jCoOHWUMA-gbbAESNRA@mail.gmail.com>
In-Reply-To
<20130402190451.GD32316@sigill.intra.peff.net>
On Tue, Apr 2, 2013 at 12:04 PM, Jeff King <peff@peff.net> wrote:
Show 11 quoted lines
> 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>
LGTM!
Reviewed-by: Garrett Cooper <yaneurabeya@gmail.com>
Previous: Jeff KingNext: Jeff King
Message 12 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.