{"thread":{"id":"10762","subject":"tracking remotes with Git","startedAt":"2007-11-09T12:44:50Z","lastAt":"2007-11-14T18:26:11Z","messageCount":6,"participants":["Ivan Shmakov","Michael Poole","Robin Rosenberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"59036","messageId":"b1e3a35f0711090444g3c31e862g4ef4ef8139927840@mail.gmail.com","threadId":"10762","inReplyTo":null,"subject":"tracking remotes with Git","fromName":"Ivan Shmakov","fromEmail":"oneingray@gmail.com","sentAt":"2007-11-09T12:44:50Z","receivedAt":"2007-11-09T12:44:50Z","isPatch":false,"sender":{"key":"oneingray@gmail.com","avatar":null},"body":"        I'm using Git (1.5.3.5 debian 1) for about a day or so, and I'm\n        quite impressed that it allows tracking remote repositories\n        (I've tried CVS and SVN) so easily with `git-cvsimport' and\n        `git-svn'.  However, I've ran into a couple of problems with\n        them:\n\n        * it looks like `git-cvsimport' uses its own CVS protocol\n          implementation which doesn't support compression; I've tried\n          to clone a repository of a project hosted in CVS since circa\n          1998 and it 20 MiB or so to obtain revisions until 2000 or so;\n          any ways to minimize traffic?\n\n        * how many revisions will `git-svn fetch' obtain from the SVN\n          repository? I had to run it for several times to get the full\n          history; I've tried to use (undocumented) `--fetch-all'\n          option, but it appears to help (may be but for a little.)\n\n        BTW, does http://.../git.git/ mean a ``bare repository (i. e., a\n        would be /git/.git/) for Git''?\n\nPS.  I wonder, if this mailing list accepts mail from unsubscribed\n        `From:'s?\n"},{"id":"59082","messageId":"87ode31iki.fsf@graviton.dyn.troilus.org","threadId":"10762","inReplyTo":"b1e3a35f0711090444g3c31e862g4ef4ef8139927840@mail.gmail.com","subject":"Re: tracking remotes with Git","fromName":"Michael Poole","fromEmail":"mdpoole@troilus.org","sentAt":"2007-11-09T16:37:17Z","receivedAt":"2007-11-09T16:37:17Z","isPatch":false,"sender":{"key":"mdpoole@troilus.org","avatar":null},"body":"Ivan Shmakov writes:\n\n>         I'm using Git (1.5.3.5 debian 1) for about a day or so, and I'm\n>         quite impressed that it allows tracking remote repositories\n>         (I've tried CVS and SVN) so easily with `git-cvsimport' and\n>         `git-svn'.  However, I've ran into a couple of problems with\n>         them:\n>\n>         * it looks like `git-cvsimport' uses its own CVS protocol\n>           implementation which doesn't support compression; I've tried\n>           to clone a repository of a project hosted in CVS since circa\n>           1998 and it 20 MiB or so to obtain revisions until 2000 or so;\n>           any ways to minimize traffic?\n\nWhat I do is arguably a horrible kludge, but it works well: rsync to\nmirror the CVS repository to my local drive, and cvsimport from that.\nWhen I was tweaking the import process (command-line options and the\nauthor conversion file), having the local copy helped a lot.\n\nMichael Poole\n"},{"id":"59104","messageId":"m2k5ormgqa.fsf@cherry.siamics.int","threadId":"10762","inReplyTo":"87ode31iki.fsf@graviton.dyn.troilus.org","subject":"Re: tracking remotes with Git","fromName":"Ivan Shmakov","fromEmail":"oneingray@gmail.com","sentAt":"2007-11-09T18:11:25Z","receivedAt":"2007-11-09T18:11:25Z","isPatch":false,"sender":{"key":"oneingray@gmail.com","avatar":null},"body":">>>>> Michael Poole <mdpoole@troilus.org> writes:\n\n[...]\n\n >> * it looks like `git-cvsimport' uses its own CVS protocol\n >> implementation which doesn't support compression; I've tried to\n >> clone a repository of a project hosted in CVS since circa 1998 and\n >> it 20 MiB or so to obtain revisions until 2000 or so; any ways to\n >> minimize traffic?\n\n > What I do is arguably a horrible kludge, but it works well: rsync\n > to mirror the CVS repository to my local drive, and cvsimport from\n > that.  When I was tweaking the import process (command-line options\n > and the author conversion file), having the local copy helped a\n > lot.\n\n\tWell, rsync certainly gives CVS the ``disconnected operation''\n\tability...  Any chances to get rsync (or scp/sftp, etc.) access\n\tto the CVS repositories on Savannah?  (I'm not one of the\n\tdevelopers of the aforementioned project, if that matters.)\n"},{"id":"59123","messageId":"200711092138.56277.robin.rosenberg.lists@dewire.com","threadId":"10762","inReplyTo":"b1e3a35f0711090444g3c31e862g4ef4ef8139927840@mail.gmail.com","subject":"Re: tracking remotes with Git","fromName":"Robin Rosenberg","fromEmail":"robin.rosenberg.lists@dewire.com","sentAt":"2007-11-09T20:38:55Z","receivedAt":"2007-11-09T20:38:55Z","isPatch":false,"sender":{"key":"robin.rosenberg@dewire.com","avatar":"https://avatars.githubusercontent.com/u/46357?v=4"},"body":"fredag 09 november 2007 skrev Ivan Shmakov:\n>         I'm using Git (1.5.3.5 debian 1) for about a day or so, and I'm\n>         quite impressed that it allows tracking remote repositories\n>         (I've tried CVS and SVN) so easily with `git-cvsimport' and\n>         `git-svn'.  However, I've ran into a couple of problems with\n>         them:\n> \n>         * it looks like `git-cvsimport' uses its own CVS protocol\n>           implementation which doesn't support compression; I've tried\n>           to clone a repository of a project hosted in CVS since circa\n>           1998 and it 20 MiB or so to obtain revisions until 2000 or so;\n>           any ways to minimize traffic?\n\nYou can pass options to cvsps.  My guess is -P \"-Z\" will do it.\n\n-- robin\n"},{"id":"59259","messageId":"m24pftmnpi.fsf@cherry.siamics.int","threadId":"10762","inReplyTo":"200711092138.56277.robin.rosenberg.lists@dewire.com","subject":"Re: tracking remotes with Git","fromName":"Ivan Shmakov","fromEmail":"ivan@theory.asu.ru","sentAt":"2007-11-11T04:05:13Z","receivedAt":"2007-11-11T04:05:13Z","isPatch":false,"sender":{"key":"ivan@theory.asu.ru","avatar":null},"body":">>>>> Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:\n\n[...]\n\n >> * it looks like `git-cvsimport' uses its own CVS protocol\n >> implementation which doesn't support compression; I've tried to\n >> clone a repository of a project hosted in CVS since circa 1998 and\n >> it 20 MiB or so to obtain revisions until 2000 or so; any ways to\n >> minimize traffic?\n\n > You can pass options to cvsps.  My guess is -P \"-Z\" will do it.\n\n\tWell, this helps somewhat.  But still, IIUC, cvsps(1) is used\n\tonly to reconstruct the ``patch sets'', and to fetch the actual\n\trevisions, `git-cvsimport' contacts the CVS repository directly:\n\n--cut: $ nl -ba git-cvsimport--\n...\n   182\tpackage CVSconn;\n   183\t# Basic CVS dialog.\n   184\t# We're only interested in connecting and downloading, so ...\n   185\t\n... not a word about the compression...\n   482\tpackage main;\n   483\t\n   484\tmy $cvs = CVSconn->new($opt_d, $cvs_tree);\n...\n   911\t\t\tprint \"Fetching $fn   v $rev\\n\" if $opt_v;\n   912\t\t\tmy ($tmpname, $size) = $cvs->file($fn,$rev);\n...\n   930\t\t\tunlink($tmpname);\n...\n--cut: $ nl -ba git-cvsimport--\n"},{"id":"59860","messageId":"m2r6isiszg.fsf@cherry.siamics.int","threadId":"10762","inReplyTo":"b1e3a35f0711090444g3c31e862g4ef4ef8139927840@mail.gmail.com","subject":"Re: tracking remotes with Git","fromName":"Ivan Shmakov","fromEmail":"ivan@theory.asu.ru","sentAt":"2007-11-14T18:26:11Z","receivedAt":"2007-11-14T18:26:11Z","isPatch":false,"sender":{"key":"ivan@theory.asu.ru","avatar":null},"body":">>>>> \"IS\" == Ivan Shmakov <oneingray@gmail.com> writes:\n\n[...]\n\n IS> * it looks like `git-cvsimport' uses its own CVS protocol\n IS> implementation which doesn't support compression; I've tried to\n IS> clone a repository of a project hosted in CVS since circa 1998 and\n IS> it 20 MiB or so to obtain revisions until 2000 or so; any ways to\n IS> minimize traffic?\n\n\tI've switched to tailor instead.  It uses native cvs(1), which\n\tsupports compression.\n\n IS> * how many revisions will `git-svn fetch' obtain from the SVN\n IS> repository?  I had to run it for several times to get the full\n IS> history; I've tried to use (undocumented) `--fetch-all' option,\n\n\tBTW, how about documenting that one?\n\n IS> but it appears to help (may be but for a little.)\n\n\ts/to/not to/.\n\n[...]\n"}]}