[IronPython] The elephant in the room: source control for IronPython

niki niki at vintech.bg
Fri Oct 29 09:53:02 CEST 2010

On 29.10.2010 09:36, Jeff Hardy wrote:
> On Thu, Oct 28, 2010 at 6:31 PM, Miguel de Icaza<miguel at novell.com>  wrote:
>> Moving to Git seems like a no brainer to me: we only have to move IronPython
>> there.   If we were to pick another of the open source source code
>> management systems we would be moving both Ruby and Python away.
> Where I'm torn is that IronPython is between a rock and a hard place -
> on the one hand, I want to work closely with the Mono project (which
> would strongly imply using github), but I also want to be in sync with
> the Python community (which has largely embraced hg).
> Python's separated stdlib will be a Mercurial repo, and if IronPython
> were in Hg we could easily pull in the stdlib as a subrepo. However, I
> presume the DLR will stay on github, and we'll need to pull that in as
> well, which of course would be easier from git.
> Damned if we do, damned if we don't. I'm leaning towards Mercurial
> because I prefer it, and it seems like many other people do as well. I
> know hg can pull from git, but I don't know about the reverse.

IIRC mercurial has git support.


More information about the Ironpython-users mailing list