Yooooooo ! > If its not merged then it is not clear which ticket it belongs to, if at all. > So thats a no. But then the real use case is that you have an already merged > commit (from git blame or git log) and you want to know the ticket.
Nono, I meant : does it work if the commit *was* merged, but was merged years ago. When you have no way to be sure that the message of the merge commit respected a specific strandard. > I don't mind integrating it in Sage but at least during the transition period > thats a bad design choice imho. HMmmmmmmmmm O_o Well, if you tried it a lot already, I don't see what's the problem. Plus I can swear I would use it too, and other probably too. Actually, with this kind of thing around I'm pretty sure no developper would use the dev scripts anymore :-P Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
