#14982: Coercion from rings with coerce_embedding into constructions over those
rings is broken
-------------------------------------------------+-------------------------
Reporter: mmezzarobba | Owner:
Type: defect | Status:
Priority: major | needs_review
Component: coercion | Milestone: sage-6.0
Keywords: embedding | Resolution:
Authors: Marc Mezzarobba | Merged in:
Report Upstream: N/A | Reviewers:
Branch: | Work issues:
u/mmezzarobba/coerce_embeddings | Commit:
Dependencies: | Stopgaps:
-------------------------------------------------+-------------------------
Comment (by SimonKing):
Replying to [comment:5 SimonKing]:
> I couldn't tell, unless you give me a pointer to the new workfow. What
do I need to do, when not a patch but a brunch (aaahm, branch...) is
given?
For example, when I look at the "commits" link, I see that there are three
commits, and only one of them seems to refer to this ticket. So, what do I
do with the other commits, review-wise? I see that there is a discussion
on sage-git on the question what exactly is to be reviewed. Would I only
review the last commit (since its commit message refers to this ticket)?
Would I review all three commits (but then I would potentially also review
dependencies that are reviewed elsewhere!)?
--
Ticket URL: <http://trac.sagemath.org/ticket/14982#comment:6>
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/groups/opt_out.
