#20136: Various meataxe build issues
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-7.1
Component: packages: optional | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: Reported upstream. Developers | Work issues:
acknowledge bug. | Commit:
Branch: | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Comment (by SimonKing):
Jeroen, I have developed my patches with a git repository on my laptop.
Since the new meataxe upstream code is at github, shouldn't it be possible
to do a merge more or less smoothly (using kdiff3 I mean)? How do I use
github, i.e., how do I pull the recent upstream changes so that I can
merge with my patches?
Or: SHOULD I do the merge? Should an optional meataxe package be based on
the latest official meataxe release (which is currently the case) or on a
non-official development branch?
--
Ticket URL: <http://trac.sagemath.org/ticket/20136#comment:11>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
