or better for the client: hg-git (http://hg-git.github.io/)
On Tuesday, December 17, 2013 1:26:23 PM UTC+1, maldun wrote: > > Why not use git-hg? https://github.com/cosmin/git-hg > > On Monday, December 16, 2013 11:51:27 AM UTC+1, Volker Braun wrote: >> >> I would recommend people change their mercurial patches to git branches, >> even only if to get their feet wet with git and the "sage -dev" scripts. >> But I will merge mercurial tickets, too. >> >> For now it is still possible to use mercurial & sage-5.13 to develop, but >> as time passes this will become less feasible. >> >> >> >> On Monday, December 16, 2013 9:56:11 AM UTC, Jeroen Demeyer wrote: >>> >>> There are various tickets having positive_review which have Mercurial >>> patches. Will these need to be changed to a git branch before they can >>> be merged or will the release manager take care of this? >>> >>> What about Mercurial patches which are currently >>> needs_work/needs_review? Can these be finished in Mercurial-world or is >>> that a bad idea? >>> >>> Jeroen. >>> >> -- 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.
