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

Re: `git fetch --refmap=<refspec>… <repository> <refspec>… ` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs

From
Johannes Sixt <j6t@kdbg.org>
Date
Sep 4, 2024, 16:38 UTC
Message-ID
<562614e4-5384-4220-896a-20b3f79771bd@kdbg.org>
In-Reply-To
<CANrWfmRdz1Xxud=f0GWrc=nURV2xZU8Wm=8u2X+W4tL4d-yeTg@mail.gmail.com>
Am 04.09.24 um 13:12 schrieb Han Jiang:
Show 5 quoted lines
> 1. If the doc says "providing an empty <refspec> to the --refmap
> option causes Git to ignore the configured refspecs and rely entirely
> on the refspecs supplied as command-line arguments" then it's
> reasonable to guess that "providing a non-empty <refspec> will not do
> those".

Fair enough. But then in section "Configured Remote-tracking Branches" it is said that "The latter use of the remote.<repository>.fetch values can be overridden by giving the --refmap=<refspec> parameter(s) on the command line." So... I dunno. Just my 2c.

-- Hannes
Previous: Han JiangNext: Junio C Hamano
Message 4 of 8 in “`git fetch --refmap=<refspec>… <repository> <refspec>…​` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs”
  1. Han JiangSep 4, 2024
  2. Johannes SixtSep 4, 2024
  3. Han JiangSep 4, 2024
  4. Johannes SixtSep 4, 2024
  5. Junio C HamanoSep 4, 2024
  6. Han JiangSep 4, 2024
  7. Junio C HamanoSep 4, 2024
  8. Han JiangSep 4, 2024

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.