Volker Braun writes: > Thats ok for reviewing tickets, and implemented as "git trac try > <ticketno>".
OK. I had a chat with Thierry Monteil and we agreed there were some subtle differences I don't remember - but I'll take a look at "git trac try". > But if you want to actually make changes then this creates a new merge > commit which furthermore is against the conventional order (where the > feature branch is the first parent). So it makes the commit history harder > to understand. I've heard arguments against "gratuitously" merging the ticket to newest release when e.g. just fixing a typo. But that seems to me to be a rather theoretical complaint, since the ticket will be merged later on anyway. I agree with the problem with the merge order which can be annoying. I don't know if there is an obscure Git command for changing that. But if the alternative is to spend tons of time recompiling every time I'm checking out a ticket, I'm not sure I'll do the trade ;-) Best, Johan -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
