On 1/24/11 7:11 AM, Darren Dale wrote:
> On Mon, Jan 24, 2011 at 8:48 AM, John Hunter<jdh2...@gmail.com>  wrote:
>> On Mon, Jan 24, 2011 at 7:18 AM, Jeff Whitaker<jsw...@fastmail.fm>  wrote:
>>
>>> Regarding basemap, what do people recommend?  Should I create a separate
>>> github project for basemap and it's data?
>> I think that would be ideal.  Unlink svn, in git you can't have full
>> featured subdirectory checkouts, and since some of the projects,
>> basemap included are too large to include with the core, the best
>> solution is to put them in a separate repository.  This complicates
>> keeping versions in sync, but it seems like the best solution.
> 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.
>
> Darren
Darren:  I think having them as separate repos under the matplotlib 
organization is fine.  If you could do that I would be grateful.

-Jeff

------------------------------------------------------------------------------
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

Reply via email to