#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Ralf Stephan
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/use__git_trac__in_the_developer_guide|
d25e69164e90e5851b0b23d49d83373420adeeae
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by kcrisman):
* status: needs_review => needs_work
Comment:
And indeed, in src/doc/en/developer/manual_git.rst there is no `section-
git-branch` nor `section-git-commit`. I'm not sure why this compiled
properly for you; I did use `./sage -docbuild developer html` because
`make doc` broke for me somewhere else with the branch switch.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:32>
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.
