> If you are exporting the most recent commit (the usual case), then you
> can skip the hg_sage.log() and use:
> hg_sage.export('tip', patch name)
Succes! Thanks guys!
> Also, if you're going to be doing much Sage development (or
> development with any other mercurial project) I highly recomme
On Jan 25, 9:54 am, Simon King wrote:
> * 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).
If you are exporting the most recent commit (the usual
Thanks, Simon; I also replied to David via sage-nt which is where he
announced the patch.
John
2009/1/25 Simon King :
>
> 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 sinc
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. W
