For the past month or two, I've been experimenting with using git to interact with the MPL subversion repository. The bottom line is that I I haven't been able to create any kind of one-to-one mapping between git branches and svnmerge.py branches. As we're using svnmerge.py on top of subversion to manage the trunk and release branches, I see this as a pretty fatal flaw.
So, while I can use git to interact with the trunk (and create and use my own feature branches locally using git), and while using git is very nice for browsing history or bisecting the revision in which a bug cropped up, I think I've reached a point where I don't think interaction with svnmerge.py's branches is going to work without investing more time than I'm willing to give into understanding (and possibly improving) git-svn. So, therefore, I'd say the issue of using a distributed version control system for MPL has not reached any real conclusion. Thus, we may want to visit this issue at some point. Perhaps once Python and/or numpy have made decisions. The Python-dev team seems to be working this out right now: http://www.python.org/dev/peps/pep-0374/ -Andrew ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
