From: "Mike Snitzer" <snitzer@gmail.com>
To: "Michael Haggerty" <mhagger@alum.mit.edu>
Cc: "Eyvind Bernhardsen" <eyvind-git-list@orakel.ntnu.no>,
"Thomas Pasch" <thomas.pasch@jentro.com>,
git@vger.kernel.org, "Jan Wielemaker" <wielemak@science.uva.nl>,
"Gerald (Jerry) Carter" <jerry@samba.org>,
dev <dev@cvs2svn.tigris.org>
Subject: Re: Problem with git-cvsimport
Date: Tue, 30 Oct 2007 16:06:09 -0400 [thread overview]
Message-ID: <170fa0d20710301306o6b3798f9k72615eb811d871f2@mail.gmail.com> (raw)
In-Reply-To: <F1176033-1C6E-43F3-9F47-3BDD5EC88A14@orakel.ntnu.no>
On 10/10/07, Eyvind Bernhardsen <eyvind-git-list@orakel.ntnu.no> wrote:
...
>
> Thanks for making cvs2svn the best CVS-to-git conversion tool :) Now
> if it would only support incremental importing...
Michael,
I second this question: is there any chance incremental importing will
be implemented in cvs2svn?
I've not used cvs2svn much and when I did it was for svn not git; but
given that git-cvsimport is known to mess up your git repo (as Eyvind
pointed out earlier) there doesn't appear to be any reliable tools to
allow for incrementally importing from cvs to git.
Are others using a tool for reliably importing from cvs to git?
next prev parent reply other threads:[~2007-10-30 20:07 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 [this message]
2007-10-30 21:15 ` Mike Snitzer
2007-10-30 21:44 ` Robin Rosenberg
2007-10-31 12:40 ` Aidan Van Dyk
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=170fa0d20710301306o6b3798f9k72615eb811d871f2@mail.gmail.com \
--to=snitzer@gmail.com \
--cc=dev@cvs2svn.tigris.org \
--cc=eyvind-git-list@orakel.ntnu.no \
--cc=git@vger.kernel.org \
--cc=jerry@samba.org \
--cc=mhagger@alum.mit.edu \
--cc=thomas.pasch@jentro.com \
--cc=wielemak@science.uva.nl \
/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).