Nick Alexander wrote: >> I think I'm not communicating my point very clearly. I'm suggesting >> that the release manager have in his patch application script an >> automated "prepend 'Trac #xxxx: ' to the commit message" step. > > I thought of implementing this but couldn't think of a way to discover > if there was a ticket number already there! (If you can do that, you > can just use it :) How do you prevent Trac #6346: fix trac #6346?
I think it's fine to have two mentions of the ticket number. The first is understood to be automated and corresponds to the actual ticket number the patch was pulled from (so is guaranteed to be correct). In fact, your example shows how commit messages might change: if you know the trac number will go on automatically, then you might give a more descriptive commit message :). Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
