Re: [PATCH v4 2/4] fetch: infer branches to fetch from a refmap-only remote

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Sep 29, 2026, 09:27 UTC
Message-ID: <CAHwyqnX2O1e+f6qss5+AL3f-Q-PHQmZjbayiph2cQiQGDjSAkA@mail.gmail.com>
In-Reply-To: <45b26e2bb292f31eb36d88e2fcf8801eb8313374.1790673598.git.gitgitgadget@gmail.com>

Show 8 quoted lines

> +test_expect_success 'a bare fetch needs nothing until a branch is tracked' '
> +       (
> +               cd client &&
> +               git fetch upstream &&
> +               git for-each-ref --format="%(refname)" refs/remotes/upstream >actual &&
> +               test_must_be_empty actual
> +       )
> +'

I still don't think it makes sense that bare 'git fetch upstream' doesn't fetch the HEAD branch to then allow me to do

    git branch --set-upstream-to=upstream

But maybe that's for another topic.

Harald

$ 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.