#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 kcrisman):
I'll think about that, thanks - as long as this isn't a ticket that has to
get merged immediately, which it seems not, I appreciate it.
As to `sage -dev command` versus `git trac command`, if they really are
nearly identical in most ways, I don't see a problem; the issue would be
if ... hold on, could one simply make `sage -dev command` equal `sage -git
trac command` in some obvious 1-1 way? (I mean that `sage -dev command`
would literally call `sage -git trac command` behind the scenes - in which
case one doesn't need to separately download git but still gets all the
benefit; I noticed git_trac in the latest sources, though perhaps that is
not a built pkg?) But I don't know if they have different functionalities
in some places. After all, if git is coming with Sage anyway, why
download it? (For the newish developer, I mean.)
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:13>
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.
