New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metaticket - improvements to the Macaulay2 interface #28573
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:4
I created a branch that merges all the tickets together to see if there was any merge conflict. There was one, but it was easy to resolve. Last 10 new commits:
|
Branch: public/interfaces/m2/28573 |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:12
Ticket retargeted after milestone closed |
comment:13
Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date. |
comment:15
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
"There are too many changes going on at once, so that a merge in the end might be difficult. In order to avoid such difficulties and to keep an overview of things that are happening (for me and others), I use this ticket from now on as a metaticket, where all latest changes are merged together." (copied from #28519).
Tickets:
CC: @saliola @dimpase @antonleykin
Component: interfaces: optional
Keywords: macaulay2, IMA Coding Sprint
Branch/Commit: public/interfaces/m2/28573 @
1368231
Issue created by migration from https://trac.sagemath.org/ticket/28573
The text was updated successfully, but these errors were encountered: