#6987: reorganize section on producing patches with Mercurial
---------------------------+------------------------------------------------
Reporter: mvngu | Owner: tba
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.1.2
Component: documentation | Keywords:
Reviewer: | Author:
Merged: |
---------------------------+------------------------------------------------
From Mariah Lenox on this [http://groups.google.com/group/sage-
support/browse_thread/thread/2c56d4cd5e4de464 sage-support] thread:
{{{
> Tutorials, tips and techniques on making and managing patches should
> go in the Developers' Guide at
>
> http://www.sagemath.org/doc/developer/
Aha! This already has the stuff I was going to write up.
The reason that I never looked at this is that I do not consider
myself
a "developer". I found the Sage documentation for sxrange/xsrange
confusing,
William suggested I write a patch for the documentation, and I tried
to do so.
The section that you referenced "Producing Patches with Mercurial" is
in the second half of the Developers' Guide. I never would have found
it without your pointing me at it.
I respectfully suggest that this section be split out to a "How to
make
a Sage patch (for newbies)" ... or at the very least moved to the
beginning
of the Developers' Guide.
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6987>
Sage <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
