#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|
86a4216fe513cc648c508788ac4f6de32ce23e8f
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
Okay, agreed on the Rosetta stone, that makes sense.
I hope it's okay if I don't immediately respond on this - I have been so
incredibly swamped, and shouldn't even really be doing anything Sage-
related, but this and the jsmol are pretty important to me - I think I can
think of a good reorganization. Mainly, this is so git-centric early on
that someone who just wants to see anything at all about what it even
would mean to help develop is lost. But `git trac` looks promising.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:18>
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.
