#6495: Build the reference manual incrementally
---------------------------------------------------------------+------------
Reporter: mpatel | Owner:
jdemeyer
Type: enhancement | Status:
needs_review
Priority: major | Milestone:
sage-5.7
Component: documentation | Resolution:
Keywords: days38 | Work issues:
Report Upstream: N/A | Reviewers:
Volker Braun, Florent Hivert
Authors: Mitesh Patel, John Palmieri, Florent Hivert | Merged in:
Dependencies: #13143, #12719 | Stopgaps:
---------------------------------------------------------------+------------
Comment (by jhpalmieri):
How about downloading
[http://sage.math.washington.edu/home/palmieri/misc/6495/sage-5.7.beta4-6495/spkg/standard/sage-5.7.beta4-6495.spkg
just the sage library spkg] (which is 57M)?
Again, I apologize for not keeping track of the dependencies. My general
reaction when a new beta comes out is to try to apply the patches, find
that they don't apply, swear a bit, and then rebase them. If someone does
something minor (say, modify `doc/en/reference/algebras.rst`), then
running the script instead of applying the "part1" patch should take care
of things. But if someone adds a new file to `doc/en/reference/`, then
several of the patch files will need to be rebased. This happened between
5.7.beta3 and 5.7.beta4.
Is there a good way with mercurial to find out all of the recent changes
to files in a certain directory? Then I could identify the dependencies
easily.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6495#comment:223>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
