Re: [sage-devel] Patch submitting procedures

2011-04-03 Thread William Stein
On Sunday, April 3, 2011, Keshav Kini wrote: > On Apr 4, 3:23 am, William Stein wrote: >> Could we change the default to "git = true" as a patch to the version >> of hg we distribute with Sage?   Or, alternatively, have a patch that >> prints a warning >> whenever Sage's hg is used but git = fals

Re: [sage-devel] Patch submitting procedures

2011-03-31 Thread Ivan Andrus
On Mar 28, 2011, at 11:36 AM, Jeroen Demeyer wrote: > 2) Patches should be made using *hg export tip*, and not hg diff. Don't forget that you need to use --git if you have touched any binary files. It may be best to add this to your .hgrc (I think this was mentioned in another thread recently)

[sage-devel] Patch submitting procedures

2011-03-28 Thread Jeroen Demeyer
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 sp