Depends on what "related" means, really. Ideally you have a directed graph of dependencies a->b->c. If you can't order the tickets then really you only have one ticket.
If you haven't shared the branches yet then it would be nice to clean up the commits, but its in no way required. Don't rewrite history on stuff that is on trac already. On Monday, June 30, 2014 3:12:58 PM UTC-4, Vincent Knight wrote: > > Dear all, > > James Campbell and I have been working on 3 related tickets ( > http://trac.sagemath.org/ticket/16331, > http://trac.sagemath.org/ticket/16332, > http://trac.sagemath.org/ticket/16333). > > We pushed 16332 to trac a while ago and have an almost positive review and > have since been busy with 16333. > > On our own repository (https://github.com/theref/sage-game-theory/) we > have some overlap between our 16332 and 16333 branches (16333 is in effect > a branch of 16332). We're now almost ready to push 16333 to trac and I just > want to check if we can push it as it is or if we're supposed to 'clean' > 16333 of any relation to 16332 so that in effect every branch on trac > corresponds to a single ticket. > > Hopefully I've explained that correctly and it's a simple enough answer. > > Thanks :) > > Vince > -- 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/d/optout.
