On Aug 26, 11:06 am, David Joyner <[email protected]> wrote:
> The way I do this (which may not be the best way) is
>
> 1. cd to the SAGE_ROOT directory
> 2. ./sage -b main (this assures you are starting from the main
> branch and not cloning form a clone)
> 3. ./sage -clone ABCDx (where ABCD is the trac number you are
> applying the patch from and x=a for the first clone,
> x=b for the second clone, if needed, and so on)
> 4. ./sage (start sage)
> 5. type hg_sage.apply("/path/to/the/patch/trac_ABCD_blahblah.patch")
It is worth pointing out that if one uses
hg_sage.import_patch("/path/.../blah.patch",options="--no-commit")
it is MUCH easier to remove the patch after you test it. That means
no more needing to make a new clone for each test, and allows people
like me to avoid using queues just a little bit longer.
- kcrisman
> 6. ctl-D (quit sage)
> 7. ./sage -b (to rebuild) or ./sage -br (to rebuild and restart sage).
>
> On Wed, Aug 26, 2009 at 7:19 AM, J. Cooley<[email protected]> wrote:
>
> > I would like to apply the patches from ticket #6384 to the clone I'm
> > using. I have not done this before and I want to make sure that I
> > apply it to the clone and not the main. I'm not entirely sure how to
> > do this.
>
> > Also, this patch seems to rely upon another from ticket #6672, so do I
> > need to add the three files from that ticket first in order and then
> > the two from ticket #6384?
>
> > Cheers.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
