On Oct 5, 2009, at 6:56 PM, Mark Lodato wrote: > On Sun, Oct 4, 2009 at 3:52 AM, Robert Bradshaw > <[email protected]> wrote: >> Just wish we had found it in one of the release candidates... > > Me too. To be honest, I didn't even know that you included > cython_freeze until I saw the release announcement.
I remember you were encouraging about including it when this first came up--we just haven't done a release since then. (Well, maybe 0.11.2, but that didn't have much new stuff.) >>> What is the best way to get these changes into Cython? I'm used to >>> the git model, where I would just post patches to the mailing list, >>> but I'm not too familiar with Hg. >> >> That model works with hg as well, though we typically don't send a >> lot of patches back and forth via email as it clutters the mailing >> list. Another thing you can do is post the patch to a ticket in trac. >> (Don't close the ticket though, or it might not get noticed and >> merged...) > > I created a git clone of the cython-devel repository and posted it > to GitHub: > > http://github.com/MarkLodato/cython/tree/freeze > > The main line is branch "master" and my changes are in branch > "freeze". As far as I can tell, "hg import" accepts git patches - is > this correct? I hope so, because I much prefer git to hg. Just out of complete curiosity, why the strong preference? (I like both for different reasons.) > If that's case, I'll post these patches to trac to make it easier > for you to > import (or whatever would be best for you). Yes, please do that. > By the way, it might be nice to have an automatic, read-only mirror on > GitHub. If you're interested in hosting the script to do this, I > would be happy to put something together for you. Sure. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
