Mike Hansen <mhan...@gmail.com> writes: > This doesn't seem to be what William wants -- he wants to make the > changes in git and be able to contribute those to Sage (as if he > hadn't used git). Other than producing patches with git and then say > qimporting them into hg, the best bet looks to be > https://github.com/offbytwo/git-hg where you can "experimentally" push > to an hg repo.
Or use hg-git - http://bitbucket.com/durin42/hg-git/ - to pull your patch into the hg Sage library. hg-git is much less experimental than git-hg, I believe. Or, you could just not use Mercurial at all and create fake Mercurial patches as I described in my response to William in this thread. This is probably the nicest option, since you don't have to mess around with multiple version control systems and conversion layers. -Keshav -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
