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

Re: [PATCH 1/1] fetch.c: fix typo in a warning message

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Nov 1, 2019, 09:48 UTC
Message-ID
<CAN0XMOLDZo06Xa-Q9qVrVNk_J3+b2sP5e30f=_9s3nUw-B_JvQ@mail.gmail.com>
In-Reply-To
<20191031225310.GA211076@google.com>
Am Do., 31. Okt. 2019 um 23:53 Uhr schrieb Jonathan Nieder <jrnieder@gmail.com>:
Show 10 quoted lines
>
> I wonder what this warning is trying to say.  How would I go about
> triggering this message?  The comment before says
>
>         The relevant upstream is the fetched branch that is meant to
>         be merged with the current one, i.e. the one fetched to
>         FETCH_HEAD.
>
> So is this about when I'm fetching with a wildcard or something?
>

The message shows up when multiple refspecs/branches are passed, like

$ git fetch --set-upstream origin master next
From https://github.com/git/git
 * branch                  master     -> FETCH_HEAD
 * branch                  next       -> FETCH_HEAD
warning: multiple branch detected, incompatible with --set-upstream
Previous: Jonathan NiederNext: Junio C Hamano
Message 4 of 5 in “fetch.c: fix typo in a warning message”
  1. 0/1 fetch.c: fix typo in a warning messageRalf Thielow via GitGitGadget, Oct 31, 2019
  2. 1/1 fetch.c: fix typo in a warning messageRalf Thielow via GitGitGadget, Oct 31, 2019
  3. Jonathan NiederOct 31, 2019
  4. Ralf ThielowNov 1, 2019
  5. Junio C HamanoNov 2, 2019

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.