On Fri, Jan 28, 2011 at 5:58 PM, Darren Dale <dsdal...@gmail.com> wrote:
>> It's not a completely fleshed out thought, but if we got the cvs repo >> before the directory move, did cvs to svn on that repo, and then >> converted that to git, we might be able to stitch the two git >> histories together, one from before the move and one after. > > That might be possible. Do you have access to the cvs repo? Apparently not > cvs -z3 -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/matplotlib co -P > matplotlib cvs [checkout aborted]: connect to cvs.sourceforge.net(216.34.181.96):2401 failed: Connection refused Amazing how fragile digital data is! Well, there isn't much real use for history that old, except it's sometimes fun to see how small mpl used to be :-) While I was poking around in git though, it was certainly nice how fast you could switch the current directory to different revisions. JDH ------------------------------------------------------------------------------ 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
