threads / discuss / 26415

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

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

## tl;dr

One message between Feb 5, 2011 and Feb 5, 2011.

replies: 0people: 1as markdown or json

Nguyen Thai Ngoc Duy· Feb 5, 2011, 04:30 UTC · lore
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

← back to recent threads