Ticket #17221
http://trac.sagemath.org/ticket/17221#comment:20
#17221 had been set to positive_review before, then reopened, another change
(2e62790e) was pushed at
2015-04-13T04:22:22-07
and then set to positive_review again.
It was closed at
2015-04-14T12:44:07-07
with the branch field set to commit id 2e62790e;
however, 2e62790e is _not_ contained in 6.7.beta0, only the previous commit
2cd08fb8.
For this concrete ticket, the solution is probably to simply open a new ticket
with the lost commit.
What is the procedure to avoid such situations or to detect such situations, if
not by chance?
(I had a similar ticket a year ago, so it is not an isolated occurrence)
Regards,
CH
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
