#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_info
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|
49ee6a57ca0520b8b279bc185b3410056dcdc747
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
I think it would be terrible to present users with two competing models.
We need to be clear which one we prefer, anything else is just confusing
to newcomers. Note that I'm fine with documenting different approaches. So
-1 to a rosetta stone, but +1 for a one-page "git cheat sheet" that you
can print out and put next to your computer.
Also, I'm against using the git install inside of Sage. That'll just cause
tears later: If `make distclean && make` didn't work you now you can't
switch branches, yay. Especially with even Xcode including git now there
really is no point.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:14>
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.
