On Tue, Apr 15, 2008 at 11:28:49PM -0400, Stephen Sinclair wrote: > On Tue, Apr 15, 2008 at 9:33 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > > (such as branch names in case of Mercurial, or branches > > descriptions in this case) > > This got me thinking... > It's a little crazy, but: since branch descriptions would essentially > just be an extension of the branch name, play basically the same role > and have the same requirements for storage, cloning, etc., what about > using some syntax in the branch name itself to separate a "short name" > and a "long name".. > > That is, you could store it as, > refs/heads/wip:work_in_progress Why not simply add the text after the sha1 in the refs/heads/branch_name file ? Obviously current and older git code should be checked to know whether they could cope with the extra data without failing... This would also have the advantage that renaming the branch would not lose the description. Mike -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
