On Wed, Feb 29, 2012 at 10:12 AM, William Stein <wst...@gmail.com> wrote:
> > It's difficult for me because they are patch in hg format, but I can't > export a patch out of git in hg format. It's possible to import the > code in from the trac ticket, but then if I make changes I have to > export them as a git diff, then import them into another hg repo, then > export them again. As far as I can tell -- no easy way to referee a > trac ticket right now using git. I bet it would be possible for a > git wizard to setup some scripts to make this easy. I think doing > so is an important first step toward moving Sage developers to git. One option might be to try to use the mercurial plugin hggit. I tried it for about 5 minutes one day to migrate from a mercurial repository to a git repository, and I never quite got it to work right for what I wanted, but in principle you should be able to use it to pull from (or push to) a git repository into (or from) a mercurial repository. So if you keep two repositories, this should at least get rid of (or automate) the intermediate step of exporting changes from git and then importing the changes into mercurial. With some more effort to figure out how to make it work right, it might make other things easier as well. -- 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
