#16331: Game Theory: Build capacity to solve matching games in to Sage.
-------------------------------------+-------------------------------------
       Reporter:  vinceknight        |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.4
      Component:  game theory        |   Resolution:
       Keywords:  Game Theory,       |    Merged in:
  Matching Games,                    |    Reviewers:
        Authors:                     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  40d4cfaa662913ca6795a8a9a598b53cf931809c
  
u/vinceknight/game_theory__build_capacity_to_solve_matching_games_in_to_sage_|  
   Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by vdelecroix):

 Replying to [comment:26 vinceknight]:
 > So to summarise what I will/need to do:
 >
 > 1. checkout a 'clean' version from the Sage master branch

 Nope. The best would be the last "develop" branch (which is
 sage.6.4.beta2)

 > 2. add in one commit the code relevant to this ticket (in effect a
 single python file)

 yes

 > 3. push to this ticket

 yes


 > Thanks for the help, I think the main problem came from working on
 multiple (related) tickets in quick succession and branching from
 completed tickets instead of the master branch.

 I agree this is always a mess. What I do is that I create a complete order
 on my tickets, i.e. ticket1 comes before ticket2, which comes before
 ticket3... Then I base ticket2 at the end of ticket1 and ticket3 and the
 end of ticket2. With the link I provided to rewrite history, it helps you
 to keep everything clean even if you have to do some rebase because of the
 reviews and/or some new beta release. Note that it might be helpful to the
 reviewer to add commit lines that looks like "ticket #XXX: change a
 doctest".

 Vincent

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

Reply via email to