From: Samuel Lucas Vaz de Mello <samuellucas@datacom.ind.br>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: git-cvsimport BUG: some commits are completely out of phase (but cvsps sees them all right)
Date: Mon, 03 Nov 2008 17:03:58 -0200 [thread overview]
Message-ID: <490F4B1E.2080707@datacom.ind.br> (raw)
In-Reply-To: <490F1021.1090002@alum.mit.edu>
Michael Haggerty wrote:
> Francis Galiegue wrote:
>> The plan would be to convert all modules in one go, with no one committing in
>> the meantime, so that's not a problem.
>
> Then you should definitely try cvs2svn/cvs2git [1]. cvsps-based
> conversion tools all have known and unavoidable problems due to the
> limitations of cvsps.
>
Michael,
Does cvs2git plans to support incremental importing?
- Samuel
next prev parent reply other threads:[~2008-11-03 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 21:03 git-cvsimport BUG: some commits are completely out of phase (but cvsps sees them all right) Francis Galiegue
2008-11-02 22:21 ` Tomi Pakarinen
2008-11-02 22:31 ` Francis Galiegue
2008-11-03 14:52 ` Michael Haggerty
2008-11-03 19:03 ` Samuel Lucas Vaz de Mello [this message]
2008-11-03 19:08 ` Shawn O. Pearce
2008-11-03 19:40 ` Michael Haggerty
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=490F4B1E.2080707@datacom.ind.br \
--to=samuellucas@datacom.ind.br \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.