#9419: Update Developers Guide to state how patches should be made.
-----------------------------+----------------------------------------------
Reporter: drkirkby | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.8
Component: documentation | Keywords: patch doc howto spkgs diff
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-----------------------------+----------------------------------------------
Comment(by drkirkby):
A minor typo, with "an" instead of "a".
"so if you are writing an spkg which is not part of the standard"
Personally I would have used:
{{{
diff -Naur
}}}
which seems one of the most common ways. There's some discussion in
http://linux.die.net/man/1/patch
of the best arguments to use. The main change is that this is recursive,
so if one edits multiple files to make a change to sort out some problem,
there can be one patch file to resolve the problem, rather than having to
make one for each file.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9419#comment:15>
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 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.
