On Wed, Mar 3, 2010 at 1:31 PM, Jonathan Taylor <jtay...@cs.toronto.edu> wrote: >> I am strongly in favor of keeping the entire commit history of >> trunk/matplotlib. While the repo is large now, most of the size comes >> from data and regression test images, and the early history is largely >> code so will not add much incremental size. I suppose one of the >> downsides of git is since you have to get the *entire* history on one >> checkout, you end up with a bunch of stuff you are unlikely to ever >> need, like data that was once in the repo but has now been removed (eg >> the stuff we migrated to sampledata). Not sure if there is an easy >> solution here. > > I think you should be able to use git clone --depth=x to get a shallow > copy of the repository. The limitation is that you cannot push from > or pull from your new repository. You can pull to it and create > patches though, which is enough for most people I think.
Tried a few options from Andrew's repo: jdhun...@uqbar:~> du -hs mpl.git* 191M mpl.git # no --depth 191M mpl.git0 # --depth=0 147M mpl.git1 # --depth=1 147M mpl.git10 # --depth=10 This compares with 87M for a clean svn checkout. So it doesn't look like a huge deal to get the whole thing compared to svn, and it looks like the --depth save very little currently. Didn't notice too much in terms of checkout time either... Thanks for the suggestion though! JDH ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
