From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steffen Prohaska <prohaska@zib.de>, Eric Blake <ebb9@byu.net>,
m4-patches@gnu.org, Jim Meyering <jim@meyering.net>,
git@vger.kernel.org
Subject: Re: cvsimport bug on branches [was: conversion to git]
Date: Fri, 21 Sep 2007 21:22:04 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709212121330.28395@racer.site> (raw)
In-Reply-To: <200709211915.35642.robin.rosenberg.lists@dewire.com>
Hi,
On Fri, 21 Sep 2007, Robin Rosenberg wrote:
> fredag 21 september 2007 skrev Linus Torvalds:
> >
> > The big advantage of git-cvsimport is that it can do incremental
> > imports, which I don't think the other methods do. But if there is any
> > choice at all, and especially if you're not that interested in the
> > incremental feature (ie you can cut over to git, and perhaps use
> > git-cvsserver to "supprt" CVS users) the other CVS importers are
> > likely to be much better.
>
> fromcvs does incremental import and it's very fast and uses much less
> memory than cvsimport. It needs the rcs files however and will not
> convert non-branch tags.
Plus you have to install Ruby. Just wanted people to know.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-21 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20070920T010842-272@post.gmane.org>
2007-09-21 1:17 ` cvsimport bug on branches [was: conversion to git] Eric Blake
2007-09-21 5:18 ` Steffen Prohaska
2007-09-21 15:42 ` Linus Torvalds
2007-09-21 17:15 ` Robin Rosenberg
2007-09-21 20:22 ` Johannes Schindelin [this message]
2007-09-21 20:42 ` Robin Rosenberg
2007-09-21 21:12 ` Johannes Schindelin
2007-09-21 23:16 ` Robin Rosenberg
2007-09-22 8:07 ` fromcvs installation [was: cvsimport bug on branches [was: conversion to git]] Steffen Prohaska
2007-09-22 15:08 ` Simon 'corecode' Schubert
2007-09-22 0:05 ` cvsimport bug on branches [was: conversion to git] Martin Langhoff
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=Pine.LNX.4.64.0709212121330.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=ebb9@byu.net \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=m4-patches@gnu.org \
--cc=prohaska@zib.de \
--cc=robin.rosenberg.lists@dewire.com \
--cc=torvalds@linux-foundation.org \
/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).