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

Re: [BUG] fetching all remote branches results in failed multiple updates

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 8, 2019, 01:09 UTC
Message-ID
<xmqqef7ikw9f.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190308000810.GA8044@chabuduo>
Alexander Huynh <alex@grande.coffee> writes:
> Thanks for the clarification! One question: should we update the documentation
> at https://git-scm.com/docs/git-fetch#CRTB to not list this as an example to
> follow?

The example itself is valuable. The way it is labeled might be misleading to some people (although personally I do not find it so). It says "Typically such a variable may look like this" and shows the fetch refspec that is given to a repository cloned from anywhere by default.

I think it might help to update the text to clearly state that the sample one is what you get in a clone without doing anything special. The example is primarily there to show you how each part of the fetch refspec is used in the operations described in the following paragraphs,and it is not there to tell you that you have to add duplicate yourself to make these things described in the following paragraphs to happen.

Previous: Alexander HuynhNext: Alexander Huynh
Message 4 of 6 in “[BUG] fetching all remote branches results in failed multiple updates”
  1. Alexander HuynhMar 7, 2019
  2. SZEDER GáborMar 7, 2019
  3. Alexander HuynhMar 8, 2019
  4. Junio C HamanoMar 8, 2019
  5. Alexander HuynhMar 13, 2019
  6. Alexander HuynhMar 14, 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.