#15279: RootSystem __init__ builds the dual twice, breaking initialization of 
non-
crystallographic root systems
----------------------------------------------+----------------------------
       Reporter:  darij                       |        Owner:
           Type:  defect                      |       Status:
       Priority:  major                       |  positive_review
      Component:  combinatorics               |    Milestone:  sage-5.13
       Keywords:  root-system, sage-combinat  |   Resolution:
        Authors:  Darij Grinberg              |    Merged in:
Report Upstream:  N/A                         |    Reviewers:  Travis
         Branch:                              |  Scrimshaw
   Dependencies:                              |  Work issues:
                                              |       Commit:
                                              |     Stopgaps:
----------------------------------------------+----------------------------

Comment (by nthiery):

 Replying to [comment:12 jdemeyer]:
 > Replying to [comment:11 nthiery]:
 > > not having to rebase constantly, like we will have with the new
 workflow
 > Why would one need to rebase less with the new workflow? A merge
 conflict is a merge conflict, and the new workflow is not going to change
 that.

 Granted, there will be as many merges as before; but unlike what we had
 with our patch queues those will be 3-way merges, so there will be better
 support from the revision control system, with less error-prone manual
 operations.

 Cheers,

--
Ticket URL: <http://trac.sagemath.org/ticket/15279#comment:13>
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.

Reply via email to