Not sure it creates a branch and everything immediately, but I use "sage -dev import-path --url <url of a patch file>" that creates a git commit representing the patch. It's quite good and fills the "author" field as it should and everything !
Though if you have several patch files on a ticket you have to add them all manually. Nathann On 17 December 2013 21:29, John Cremona <john.crem...@gmail.com> wrote: > Could someone point me to the instructions for converting an old > non-git ticket with mercurial patches to a new-style ticket where > there's a git branch instead? I am sure that I read it somewhere but > cannot find it. > > John > > -- > You received this message because you are subscribed to the Google Groups > "sage-git" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-git+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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.
