tracking remotes with Git

        I'm using Git (1.5.3.5 debian 1) for about a day or so, and I'm
        quite impressed that it allows tracking remote repositories
        (I've tried CVS and SVN) so easily with `git-cvsimport' and
        `git-svn'.  However, I've ran into a couple of problems with
        them:

        * it looks like `git-cvsimport' uses its own CVS protocol
          implementation which doesn't support compression; I've tried
          to clone a repository of a project hosted in CVS since circa
          1998 and it 20 MiB or so to obtain revisions until 2000 or so;
          any ways to minimize traffic?

        * how many revisions will `git-svn fetch' obtain from the SVN
          repository? I had to run it for several times to get the full
          history; I've tried to use (undocumented) `--fetch-all'
          option, but it appears to help (may be but for a little.)

        BTW, does http://.../git.git/ mean a ``bare repository (i. e., a
        would be /git/.git/) for Git''?

PS.  I wonder, if this mailing list accepts mail from unsubscribed
        `From:'s?

Ivan Shmakov writes:

What I do is arguably a horrible kludge, but it works well: rsync to mirror the CVS repository to my local drive, and cvsimport from that. When I was tweaking the import process (command-line options and the author conversion file), having the local copy helped a lot.

Michael Poole

[...]

 >> * it looks like `git-cvsimport' uses its own CVS protocol
 >> implementation which doesn't support compression; I've tried to
 >> clone a repository of a project hosted in CVS since circa 1998 and
 >> it 20 MiB or so to obtain revisions until 2000 or so; any ways to
 >> minimize traffic?

 > What I do is arguably a horrible kludge, but it works well: rsync
 > to mirror the CVS repository to my local drive, and cvsimport from
 > that.  When I was tweaking the import process (command-line options
 > and the author conversion file), having the local copy helped a
 > lot.

	Well, rsync certainly gives CVS the ``disconnected operation''
	ability...  Any chances to get rsync (or scp/sftp, etc.) access
	to the CVS repositories on Savannah?  (I'm not one of the
	developers of the aforementioned project, if that matters.)

fredag 09 november 2007 skrev Ivan Shmakov:

You can pass options to cvsps.  My guess is -P "-Z" will do it.

-- robin

[...]

 >> * it looks like `git-cvsimport' uses its own CVS protocol
 >> implementation which doesn't support compression; I've tried to
 >> clone a repository of a project hosted in CVS since circa 1998 and
 >> it 20 MiB or so to obtain revisions until 2000 or so; any ways to
 >> minimize traffic?

 > You can pass options to cvsps.  My guess is -P "-Z" will do it.

	Well, this helps somewhat.  But still, IIUC, cvsps(1) is used
	only to reconstruct the ``patch sets'', and to fetch the actual
	revisions, `git-cvsimport' contacts the CVS repository directly:

--cut: $ nl -ba git-cvsimport--
...
   182	package CVSconn;
   183	# Basic CVS dialog.
   184	# We're only interested in connecting and downloading, so ...
   185	
... not a word about the compression...
   482	package main;
   483	
   484	my $cvs = CVSconn->new($opt_d, $cvs_tree);
...
   911			print "Fetching $fn   v $rev\n" if $opt_v;
   912			my ($tmpname, $size) = $cvs->file($fn,$rev);
...
   930			unlink($tmpname);
...
--cut: $ nl -ba git-cvsimport--

[...]

 IS> * it looks like `git-cvsimport' uses its own CVS protocol
 IS> implementation which doesn't support compression; I've tried to
 IS> clone a repository of a project hosted in CVS since circa 1998 and
 IS> it 20 MiB or so to obtain revisions until 2000 or so; any ways to
 IS> minimize traffic?

	I've switched to tailor instead.  It uses native cvs(1), which
	supports compression.

 IS> * how many revisions will `git-svn fetch' obtain from the SVN
 IS> repository?  I had to run it for several times to get the full
 IS> history; I've tried to use (undocumented) `--fetch-all' option,

	BTW, how about documenting that one?

 IS> but it appears to help (may be but for a little.)

	s/to/not to/.

[...]