Re: [PATCH v6 06/10] fast-export: add new --refspec option

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 12, 2013, 21:46 UTC
Message-ID: <xmqq38n1guo8.fsf@gitster.dls.corp.google.com>
In-Reply-To: <5282977b2ecd_3b98795e785e@nysa.notmuch>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 11 quoted lines

> Does it?
>
>  % git config remote.origin.fetch '+refs/heads/*:refs/remotes-test/origin/*'
>  % git fetch origin master
>  From /home/felipec/dev/git
>   * branch            master     -> FETCH_HEAD
>   * [new branch]      master     -> refs/remotes-test/origin/master
>
> In this case remote.origin.fetch is determining how to translate ref names, not
> what gets transferred, *exactly* the same as we are doing with --refspec. And
> as far as I know, remote.origin.fetch is a refspec.

If you had 'next' and 'pu' branches at the remote, do they get fetched with that command line?

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