{"thread":{"id":"26415","subject":"nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)","startedAt":"2011-02-05T04:30:25Z","lastAt":"2011-02-05T04:30:25Z","messageCount":1,"participants":["Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"160425","messageId":"AANLkTin+VLTf62NHSdAb61qEckrsLMg+s-hnWHb0HLna@mail.gmail.com","threadId":"26415","inReplyTo":null,"subject":"nesting refs (Re: [1.8.0] Provide proper remote ref namespaces)","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2011-02-05T04:30:25Z","receivedAt":"2011-02-05T04:30:25Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Sat, Feb 5, 2011 at 5:39 AM, Junio C Hamano <gitster@pobox.com> wrote:\n> While you are talking about drastic reorganization (and rewriting the ref\n> code to support it), another possible Sub-proposal we may want to consider\n> is to allow \"next\" and \"next/foo\" at the same time.\n\nOh yeah.. how about \"next/.ref\" and \"next/foo/.ref\"? Ref search code\ncan be modified to check both \"next\" and \"next/.ref\" when \"next\" is\nrequested. Old git basically won't work with new ref style, so there's\nnot much compatibility issue.\n\nWe can also add \"next/.summary\" to save a brief description of a ref.\nBut then it would be lost in packed-refs, hm..\n-- \nDuy\n"}]}