This is a reminder on how to properly submit a patch to Trac. Recently, I find a lot of small administrative issues. Please keep in mind the following:
1) When submitting a patch, make sure there is reasonable *commit message* (use hg qrefresh -e to set the message). The message is allowed to span multiple lines, but the first line should stand by itself (this will be displayed by hg log). Also the correct(!) ticket number should appear on the first line of the commit message. Long lines should be wrapped. 2) Patches should be made using *hg export tip*, and not hg diff. 3) When authoring or reviewing a ticket, add your *real name* as Author/Reviewer. Also add your name to http://trac.sagemath.org/sage_trac/#AccountNamesmappedtoRealNames 4) Write instructions for merging the patches (which patches to apply, which dependencies there are, URLs of spkgs) in the *ticket description*, not only in a comment. Thanks, Jeroen. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
