On Thu, Feb 10, 2011 at 5:54 PM, Pauli Virtanen <p...@iki.fi> wrote: > On Thu, 10 Feb 2011 17:34:32 -0500, Darren Dale wrote: > [clip] >> Unfortunately, I am getting exactly the same results: the matplotlib/ >> directory is missing in the earliest history. I've tried adding >> --use-cvs and --keep-trivial-imports, to no avail. I've tried checking >> out a working copy of the cvs repo (setting CVSROOT to point to the >> directory I created using rsync), and I *thought* the right way to >> inspect the r7 working directory is to do "cvs update -R -r 7", but >> thats not right. So I'm currently having trouble determining whether the >> history even exists in CVS. Anybody have a longer memory than I do? How >> can I get cvs to perform this basic operation? > > Maybe you can try skipping SVN altogether (needs "git-cvs" package on > Ubuntu): > > export CVSROOT=/rsynced/directory > test -d "$CVSROOT/CVSROOT" || echo "Wrong cvsroot..." > mkdir imported > cd imported > git cvsimport matplotlib > > This at least shows some files in the first revisions. You can probably > then just graft the two histories together at a suitable point. > > Apparently, it also needs some use of "git filter-branch" to get rid of > the top-level matplotlib/ directory.
On further inspection, the direct cvs to git conversion *also* yields a repository lacking the matplotlib package directory. It looks like the history leading up to revision 540 may have been lost from the CVS repository itself, not during the cvs2svn conversion. John, do you want some time to continue looking into the cvs repo yourself? Or should we go ahead with the git migration? If the latter, should we start the git repo at revision 540, or include all available history, even though some of it is missing the matplotlib package directory? If we want to go ahead with the git migration, I can probably work on it this weekend. Darren ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
