trac merely shows the commits in the branch on the ticket (relative to the latest beta). It's up to you to maintain and push branches relevant to the tickets you work on (there are cases where you want to make tickets depend upon each other, otherwise it's better to have separate branches for different tickets, so that they can be independently and simultaneosuly reviewed)
In this particular case, you don't have to worry about #21554, as it is already closed and merged by the release manager, and will appear in the next beta. As a way out, I've set the dependencies on #21946 and #22312. On Friday, March 10, 2017 at 4:57:30 AM UTC, Ashutosh Ahelleya wrote: > > Hello, > > Yesterday, I fixed an issue #22312 > <https://trac.sagemath.org/ticket/22312>, where I just changed the > documentation required and commit the changes to push them. After I changed > the Author to "Ashutosh Ahelleya" (i.e. my name), in the comments section, > the message showed all the commits that I had pushed before that are yet to > be patched. All the commits are of different issues and they are just > showing up in the comments section of that ticket. I wanted to ask if what > is displayed in the commits is correct or is there another way of pushing > the changes such that only the commit of the ticket which is being fixed is > displayed in the comments section. > > Thanks and Regards, > Ashutosh Ahelleya > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
