{"thread":{"id":"47124","subject":"benefits of \"/\" in branch names other than the obvious?","startedAt":"2017-11-06T05:37:15Z","lastAt":"2017-11-06T17:50:47Z","messageCount":2,"participants":["Robert P. J. Day","Stefan Beller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"331908","messageId":"alpine.LFD.2.21.1711060733510.13383@localhost.localdomain","threadId":"47124","inReplyTo":null,"subject":"benefits of \"/\" in branch names other than the obvious?","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2017-11-06T05:36:56Z","receivedAt":"2017-11-06T05:37:15Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"\n  another picky question ... are there any other benefits of\nsupporting slashes in branch names other than the obvious ones i know\nabout?\n\n1) visually, let's you *imagine* a branch hierarchy, and\n2) allows wildcarding on a full \"component\" basis\n\n  are there any other benefits of the above? thank you kindly.\n\nrday\n\n-- \n\n========================================================================\nRobert P. J. Day                                 Ottawa, Ontario, CANADA\n                        http://crashcourse.ca\n\nTwitter:                                       http://twitter.com/rpjday\nLinkedIn:                               http://ca.linkedin.com/in/rpjday\n========================================================================\n"},{"id":"331930","messageId":"CAGZ79kZqRV2Sui5-XRcukZiucKzv+DvRr3x3-=dHaxB5ZC6LyQ@mail.gmail.com","threadId":"47124","inReplyTo":"alpine.LFD.2.21.1711060733510.13383@localhost.localdomain","subject":"Re: benefits of \"/\" in branch names other than the obvious?","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-11-06T17:50:40Z","receivedAt":"2017-11-06T17:50:47Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Sun, Nov 5, 2017 at 9:36 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:\n>\n>   another picky question ... are there any other benefits of\n> supporting slashes in branch names other than the obvious ones i know\n> about?\n>\n> 1) visually, let's you *imagine* a branch hierarchy, and\n> 2) allows wildcarding on a full \"component\" basis\n>\n>   are there any other benefits of the above? thank you kindly.\n>\n> rday\n\nCurrently refs are stored either in .git/packed_refs,\nor the refs are taken as a literal filename (refs/heads/master\nis found in .git/refs/heads/master).\n\nWhen stored as literal files on disk there are interesting implications:\n* File System speed when there are *lots* of refs\n  (a lot of files in one dir vs sharding or a tree like structure)\n*  Directory/conflicts in the data model:\n    What if you want to have a ref foo/bar as well as foo?\n    This is not possible as 'foo' must be either a directory\n    or a file. This spawns occasional issues such as\nhttps://public-inbox.org/git/20171024082409.smwsd6pla64jjlua@sigill.intra.peff.net/\n"}]}