#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|
d25e69164e90e5851b0b23d49d83373420adeeae
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Andrey: I recently added a "git trac browse" command that'll open the trac
web page of the current ticket. I'm not sure if that should be done
automatically after a ticket creation; Especially for simple changes I
prefer to open the ticket, work on the code, then fill out the details on
the web page. Though one can certainly argue that the browser should be
opened first. But in the end I think less is more.
Tab completion is a shell feature. I've addressed the other comments in my
last commit.
Karl-Dieter: I'm definitely interested in making it more accessible to
newcomers, but I suggest we do it on a followup ticket.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:29>
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.
