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
AHAlexander Huynh <alex@grande.coffee>
Date
Mar 14, 2019, 17:20 UTC
Message-ID
<20190314172032.GA10461@chabuduo>
In-Reply-To
<20190313234524.GA3053@chabuduo>
Hi all,

Sorry to bother one last time. After a bit more digging, I found that the problem was with my workflow.

Shallow clones set `remote.origin.fetch` to one branch, so what I was doing in the past was overriding the respository-specific `remote.origin.fetch` with my global config.

I've now changed my workflow to perform a shallow clone at first, `cd` into the repository, and locally set `remote.origin.fetch` to `+refs/heads/*:refs/remotes/origin/*`.

Thanks again, Alex

Previous: Alexander Huynh
Message 6 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.