> > 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.
>
> You don't have to do that. You can do:
>
> sage: hg_sage.apply('... url ...')
> sage: quit
>
> ./sage -br
>
> sage: <try it out>
> This needs work! Argh.
> sage: hg_sage.rollback()
> sage: hg_sage.revert('--all')
> sage: quit
>
> Now your repo is as if you never applied the patch.
>
> You can only rollback one time though, so you can't apply multiple
> patches -- if you want to to that you need to clone or use queues.
>
Yes, except with the --no-commit option, I just have to revert, not
rollback. That not only saves a step, it means I could theoretically
apply several patches without a commit, and then revert them all at
once. Right? I haven't actually tried doing that... but as I said,
it's all because I need a personal queues tutorial session before I
use them.
- kcrisman
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
