On Tuesday, December 17, 2013 12:43:54 PM UTC-8, Michael Orlitzky wrote: > > It's the same as starting a new ticket/branch. When you get to the point > where you would modify the sage library, download the mercurial patch > and apply it.
This step, including the committing in git, can be done with sage --dev import-patch --url <URL> where <URL> can be the URL for the patch on trac (the raw one of course!). Once you're done, you can push the branch to trac (how to get the sage-dev scripts to understand what ticket your local branch should be attached to depends on how you started your branch) to make the ticket into a new "git" ticket, which I guess now should happen with every ticket before it can get resolved. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
