Thanks, Simon;  I also replied to David via sage-nt which is where he
announced the patch.

John

2009/1/25 Simon King <[email protected]>:
>
> Dear David,
>
> David Møller Hansen schrieb:
>> I have just done hg_sage.ci() in my modified branch. Is my patch then
>> sent to the sagemath.org? At first I thought so since the modification
>> showed up when i wrote hg_sage.serve(), but when I tried to pull in my
>> main branch I did'nt get my patch. Was my commit only local?
>
> Yes, the mercurial repository is only local.
>
> To my knowledge (but other people might know better) the usual
> procedure to get something into the Sage release is as follows:
>  * make your local changes, run "sage -b" to rebuild, test it etc.
>  * do hg_sage.commit(), in order to inform mercurial that you really
> want these changes
>  * with hg_sage.log(), look up the version number of your changes
>  * do hg_sage.export(version number, patch name). This produces a text
> file explaining your changes (this is the preferred format).
>
> The above was completely local. If you have an account for the sage
> trac, then submit the patch created with hg_sage.export there. Of
> course, you should describe the purpose of your changes. Of course, if
> your patch is a fix of a known bug, it should be attached to the
> corresponding old ticket; otherwise, open a new one.
>
> You should also change the description of the ticket: It should start
> with [with patch, needs review].
>
> There is a peer review procedure: Hopefully there will be other people
> testing you patch and providing a report. If the report is positive
> then some authorized person (e.g. Michael Abshoff) might merge your
> patch into the Sage distribution and close the ticket.
>
> Yours
>     Simon
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to