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

nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Feb 5, 2011, 04:30 UTC
Message-ID
<AANLkTin+VLTf62NHSdAb61qEckrsLMg+s-hnWHb0HLna@mail.gmail.com>
On Sat, Feb 5, 2011 at 5:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
> While you are talking about drastic reorganization (and rewriting the ref
> code to support it), another possible Sub-proposal we may want to consider
> is to allow "next" and "next/foo" at the same time.

Oh yeah.. how about "next/.ref" and "next/foo/.ref"? Ref search code can be modified to check both "next" and "next/.ref" when "next" is requested. Old git basically won't work with new ref style, so there's not much compatibility issue.

We can also add "next/.summary" to save a brief description of a ref. But then it would be lost in packed-refs, hm..

-- 
Duy
Message 1 of 1 in “nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)”
  1. Nguyen Thai Ngoc DuyFeb 5, 2011

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.