* nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)
@ 2011-02-05 4:30 Nguyen Thai Ngoc Duy
0 siblings, 0 replies; only message in thread
From: Nguyen Thai Ngoc Duy @ 2011-02-05 4:30 UTC (permalink / raw)
To: Junio C Hamano
Cc: Johan Herland, git, Sverre Rabbelier, Jeff King, Nicolas Pitre
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-02-05 4:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-05 4:30 nesting refs (Re: [1.8.0] Provide proper remote ref namespaces) Nguyen Thai Ngoc Duy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).