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

1 messages from 2011-02-05 to 2011-02-05. Participants: Nguyen Thai Ngoc Duy.
Thread: https://gitlist.dev/t/26415

## Nguyen Thai Ngoc Duy, 2011-02-05 04:30

Subject: nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)
Message-ID: <AANLkTin+VLTf62NHSdAb61qEckrsLMg+s-hnWHb0HLna@mail.gmail.com>
URL: https://gitlist.dev/e/AANLkTin%2BVLTf62NHSdAb61qEckrsLMg%2Bs-hnWHb0HLna%40mail.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

```
