Avery Pennarun: > 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. That's exactly what I do for one of the projects I am working on (well, minus the "bug-" prefix, that's implied). Bash completion works quite well for that, and the merge commits do give meaningful information. But I would still like to be able to annotate it. Especially for long-living bug-fix branches, it could be useful to be able to add describe a branch with what state it is in, for instance. -- \\// Peter - http://www.softwolves.pp.se/ -- 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
