git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aidan Van Dyk <aidan@highrise.ca>
To: dev@rapidsvn.tigris.org
Cc: git@vger.kernel.org
Subject: Re: Problem with git-cvsimport
Date: Wed, 31 Oct 2007 08:40:29 -0400	[thread overview]
Message-ID: <fg9t3t$kc3$1@ger.gmane.org> (raw)
In-Reply-To: 200710302244.50034.robin.rosenberg.lists@dewire.com

Robin Rosenberg wrote:

> I use fromcvs which is *very* fast, and quite memory conservative compared
> to the others and seems reliable so far (six months). It probably breaks
> on exotic variants of branches though, but I don't have those / don't care
> about them.

I actually use fromcvs for a few repositories, and actually started using it
on repositories where cvsps (and git-cvsimport) fail.

> Drawbacks, more dependencies and access to the rcs files is required and
> tags are not converted.

Most projects have "rsyncs" or "tarballs" of their CVS repository available,
making fromcvs possible on most of them.  And CVS tags, well they are about
as good as CVS $Keywords$.

  reply	other threads:[~2007-10-31 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  9:25 Problem with git-cvsimport Thomas Pasch
2007-10-09 12:47 ` Jan Wielemaker
2007-10-09 13:21   ` Gerald (Jerry) Carter
2007-10-09 19:41     ` Eyvind Bernhardsen
2007-10-10  2:34       ` Michael Haggerty
2007-10-10 13:05         ` Eyvind Bernhardsen
2007-10-30 20:06           ` Mike Snitzer
2007-10-30 21:15             ` Mike Snitzer
2007-10-30 21:44             ` Robin Rosenberg
2007-10-31 12:40               ` Aidan Van Dyk [this message]
2007-10-31  4:42             ` Michael Haggerty
  -- strict thread matches above, loose matches on Subject: below --
2006-10-02  9:15 problem " picca

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='fg9t3t$kc3$1@ger.gmane.org' \
    --to=aidan@highrise.ca \
    --cc=dev@rapidsvn.tigris.org \
    --cc=git@vger.kernel.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).