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

Re: Idea: Git Bundle V3 capability @HEAD=ref/heads/<name>

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 6, 2022, 18:45 UTC
Message-ID
<xmqq7d1clrjh.fsf@gitster.g>
In-Reply-To
<037901f1-1649-1485-a853-9783b9d43b31@iee.email>
Philip Oakley <philipoakley@iee.email> writes:
Show 8 quoted lines
> In brian's recent work on V3 bundles [1, et al] I spotted a potential
> idea for resolving the long standing problem that the bundle code may
> need to guess at which ref HEAD was pointed [2, et al] at when there
> were two branches that pointed at the same HEAD oid.
>
> The basic idea is to utilise the new 'capabilities' field to pass the
> particular ref that is HEAD using a 'HEAD' capability
> i.e. sending the capability    @HEAD=ref/heads/<name>

Whatever you do, I think it should model what the protocol between "git fetch" and "git upload-pack" use to convey where the symbolic refs point at.

Previous: Philip OakleyNext: brian m. carlson
Message 2 of 3 in “Idea: Git Bundle V3 capability @HEAD=ref/heads/<name>”
  1. Philip OakleyOct 6, 2022
  2. Junio C HamanoOct 6, 2022
  3. brian m. carlsonOct 7, 2022

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.