On Mon, Jan 24, 2011 at 9:18 AM, John Hunter <jdh2...@gmail.com> wrote: > On Mon, Jan 24, 2011 at 8:11 AM, Darren Dale <dsdal...@gmail.com> wrote: > >> That said, I have the conversion routines set up right now to create a >> separate "toolkits" repository, which currently includes all the >> contents of trunk/toolkits. I can tailor this further to split the >> toolkits up and create a repository for each, if thats how people want >> to do it. Those repos could either be hosted as separate repositories >> under the matplotlib github organization, or maybe better as a >> repository under a separate github project. In case of the latter, I >> can temporarily publish the repository at my own account, long enough >> for Jeff to clone it (don't fork it using githubs fork button!) and >> push it to its final destination. > > I think mplsize should just be moved into lib/mpl_toolkits so it can > be picked up by a default mpl installation. It's small enough that it > probably doesn't need it's own repo. What do you think Andrew?
I guess this can be done after the conversion: split it into its own repo, fix the hierarchy and then do an external merge from that repo to draw it into the matplotlib repo under lib/mpl_toolkits. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
