#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_review
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|
e1137d978ed581d0819f8a83a9da5dcc4c8755de
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
> I should probably add a quick section in the beginning about the `sage
-b` vs `make` thing, will do that right now.
Yes, that is a very good catch - I'm still confused about it myself!
I think that through the course of today I can make some minimal changes
with respect to organization that would make it just a little clearer
without putting `sage -dev` in a position of prominence. For instance,
it's confusing that `git-trac.html` is in the initial area (should it be
"collaborative", not "collaborate", development?). Is that reasonable?
At this point you have some other input so I'm not trying to hold it up,
but would prefer to make sure a new person can read this in order, at
least; other stuff can wait at this point.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:38>
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.
