git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Shmakov <ivan@theory.asu.ru>
To: git@vger.kernel.org
Cc: Ivan Shmakov <oneingray@gmail.com>
Subject: Re: tracking remotes with Git
Date: 11 Nov 2007 10:05:13 +0600	[thread overview]
Message-ID: <m24pftmnpi.fsf@cherry.siamics.int> (raw)
In-Reply-To: <200711092138.56277.robin.rosenberg.lists@dewire.com>

>>>>> Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:

[...]

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

  reply	other threads:[~2007-11-11  4:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 12:44 tracking remotes with Git Ivan Shmakov
2007-11-09 16:37 ` Michael Poole
2007-11-09 18:11   ` Ivan Shmakov
2007-11-09 20:38 ` Robin Rosenberg
2007-11-11  4:05   ` Ivan Shmakov [this message]
2007-11-14 18:26 ` Ivan Shmakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m24pftmnpi.fsf@cherry.siamics.int \
    --to=ivan@theory.asu.ru \
    --cc=git@vger.kernel.org \
    --cc=oneingray@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).