#14306: regression in solve
-------------------------------------+-------------------------------------
Reporter: zimmerma | Owner: burcin
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: calculus | Resolution:
Keywords: | Merged in:
Authors: Karl-Dieter | Reviewers:
Crisman | Work issues:
Report Upstream: Fixed upstream, | Commit:
in a later stable release. | 058530226b99dbb70136bec21225f0f3153f9dc0
Branch: | Stopgaps:
u/kcrisman/14306-maxima_solve_doctest|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by nbruin):
Replying to [comment:16 kcrisman]:
> <rant>I just want to point out that in Mercurial, I could always "roll
back" the previous commit and fix such trivialities. Now it has to
clutter up the log/tree/directed acyclic graph/whatever for a one-
character fix.</rant>
You still can. You'll just have to "force push" and deal with a grumpy
Volker. It's a trade-off: do you want a clean history or a (small) chance
for more difficult merge issues later on, in case someone based some work
on your now abandoned commit?
--
Ticket URL: <http://trac.sagemath.org/ticket/14306#comment:17>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
