On 10/8/08, Junio C Hamano <gitster@xxxxxxxxx> wrote: > David Soria Parra <sn_@xxxxxxx> writes: > > >> Any opinions on this? > > > > would be great to have something like that build in git-core like > > > > git branch -i 'Fix bla' ds/fix next > > git branch -i > > ds/fix (Fix Bla) > > Haven't people watched Linus on google tech talk? Here is an excerpt from > the transcript (http://git.or.cz/gitwiki/LinusTalk200705Transcript): > > ... well actually you shouldn't call it "test", you should basically > name your branches the way you name your functions, you should call > them something short and sweet and to the point -- What is that branch > doing. > > IOW, why did you name the branch "ds/fix" and not "ds/fix-bla"? Because it would be excessive typing every time you want to do something to that branch? I guess bash completions would help with this (if you're using bash), but even then it's kind of unreasonable to name branches something like "bug-111234-widget-performance-improvements-for-customer-x", which is the sort of information that would be awfully helpful two months later when you're looking at old unmerged branches. Avery -- 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
