#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 jdemeyer):
Replying to [comment:20 SimonKing]:
> I am not so much of a git expert. The upstream repository's first commit
is close to the sources my patches are based upon. Would it perhaps be
feasible to apply my patches to them, and then try to rebase the full
upstream branch?
I would not literally "rebase" but instead `git merge` the latest upstream
branch and then fix the conflicts.
> Can that be easier than the attempt to apply my patches directly to the
latest upstream commit?
Perhaps yes. You can try and see what it gives.
--
Ticket URL: <http://trac.sagemath.org/ticket/20136#comment:21>
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.
