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

git-clone --config remote.origin.fetch regression

From
Han-Wen Nienhuys <hanwen@google.com>
Date
May 28, 2019, 22:34 UTC
Message-ID
<CAFQ2z_O7rupGS4rntiUwJCHUj3bO0U88bVAToveEo_uU0Eu96w@mail.gmail.com>
(see also https://github.com/google/zoekt/issues/81)
It looks like git 2.21 included a regression. The command
git clone --bare --progress \
  --config "remote.origin.fetch=+refs/heads/*:refs/heads/*" \
  https://github.com/google/zoekt.git \
  /tmp/zoekt-git2.20.git
would succeed with git 2.20, but fails with
 fatal: multiple updates for ref 'refs/heads/master' not allowed
in git 2.21, probably caused by commit 515be83.

Should I call git in another way? I originally included "remote.origin.fetch=+refs/heads/*:refs/heads/*" to avoid getting Gerrit refs (refs/changes/*), but maybe I should use a different incantation?

-- Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

Next: SZEDER Gábor
Message 1 of 2 in “git-clone --config remote.origin.fetch regression”
  1. Han-Wen NienhuysMay 28, 2019
  2. SZEDER GáborMay 29, 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.