> 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 recommend
> learning about Mercurial queues.
I'll do this, actually never heard about the Mercurial project before
I started using Sage.
/David
On Jan 25, 9:35 pm, Carl Witty <carl.wi...@gmail.com> wrote:
> On Jan 25, 9:54 am, Simon King <k...@mathematik.uni-jena.de> 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 case), then you
> can skip the hg_sage.log() and use:
> hg_sage.export('tip', patch name)
>
> Also, if you're going to be doing much Sage development (or
> development with any other mercurial project) I highly recommend
> learning about Mercurial queues.
>
> Carl
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
