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

Re: [PATCH v2] remote: make refspec follow the same disambiguation rule as local refs

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 2, 2018, 02:26 UTC
Message-ID
<20180802022603.GE189024@aiede.svl.corp.google.com>
In-Reply-To
<xmqqo9el4ige.fsf@gitster-ct.c.googlers.com>
Junio C Hamano wrote:
Show 9 quoted lines
> One thing I forgot to mention.
>
> When asking to fetch T, in order to be able to favor refs/tags/T
> over refs/heads/T at the fetching end, you would have to be able to
> *see* both, so all 6 variants "T", "refs/tags/T", "refs/heads/T",
> "refs/remotes/T", "refs/remotes/T/HEAD" must be asked to be shown
> when the ls-remote limiting is in effect.  Since the ls-remote
> filtering is relatively new development, we may further find subtle
> remaining bugs, if there still are some.
Fortunately, the fetch code does already do that. ;-)
Jonathan
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 7 in “remote: make refspec follow the same disambiguation rule as local refs”
  1. remote: make refspec follow the same disambiguation rule as local refsJunio C Hamano, Aug 1, 2018
  2. Jonathan TanAug 1, 2018
  3. Junio C HamanoAug 1, 2018
  4. Jonathan NiederAug 1, 2018
  5. Junio C HamanoAug 2, 2018
  6. Jonathan NiederAug 2, 2018
  7. remote: make refspec follow the same disambiguation rule as local refsJunio C Hamano, Aug 2, 2018

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.