On Wednesday, October 21, 2009 at 15:37:03 (+0200) Patrick Schoenfeld writes: >Hi, > >I regulary work with various branches, that I call by the number >of an associated bug tracking / support tracking number. That >makes it clear to which ticket a given branch belongs. >In this case I would find it very useful, if I could associate >short comments with a branch, which would be shown when >doing a 'git branch'. This way I could see what this branch >about, without looking up the ticket information. > >Obvious the workaround is to name the branches different, >but this is sometimes not convenient and may result in quiet >long branch names. For now, we do just this. We use Jira for bug reporting. When we create a new Jira bug, we use the Jira Id as the base and then tack on a short suffix: % git checkout -b ADM-417_service_deploy_race_condition We are also working on tools that would, among other things, obviate this. For example: % git branch * ADM-417 ADM-312 master % jira describe ADM-417: Service deployments have logging race condition on first start % jira describe -l ADM-312 ADM-312: Portal permissions set incorrectly for WEP users Description: The portal permissions get whacked whenever ... Assigned To: John Smith <jsmith@xxxxxxxxxxxx> Status: In Progress [...] The 'jira' command just connects to our Jira server and performs actions directly on the Jira server for current or whichever branch, etc. Bill -- 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