git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Lucas Vaz de Mello <samuellucas@datacom.ind.br>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] Add more tests of cvsimport
Date: Fri, 20 Feb 2009 18:26:54 -0300	[thread overview]
Message-ID: <499F201E.2050106@datacom.ind.br> (raw)
In-Reply-To: <499E8432.9010806@alum.mit.edu>

Michael Haggerty wrote:
> BTW, I don't want to trash "git cvsimport".  I'm not brave enough even
> to try to implement incremental conversions in cvs2git.  So the fact

Michael,

If I run cvs2git several times against a live cvs repo (using the same configuration), wouldn't it perform an incremental import?
Is there anything that would make it produce different commits for the history?

I've just made a simple test here performing 2 imports (the 2nd with a dozen of new commits not in the 1st) and it seemed to work fine.

I know that it will take the same time/memory as the first import, but is there something that can break the repository or produce wrong data?

Thanks,

 - Samuel

  parent reply	other threads:[~2009-02-20 21:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  5:18 [PATCH 0/4] Add more tests of cvsimport Michael Haggerty
2009-02-20  5:18 ` [PATCH 1/4] Start a library for cvsimport-related tests Michael Haggerty
2009-02-20  5:18   ` [PATCH 2/4] Use CVS's -f option if available (ignore user's ~/.cvsrc file) Michael Haggerty
2009-02-20  5:18     ` [PATCH 3/4] Test contents of entire cvsimported "master" tree contents Michael Haggerty
2009-02-20  5:18       ` [PATCH 4/4] Add some tests of git-cvsimport's handling of vendor branches Michael Haggerty
2009-02-20  6:25 ` [PATCH 0/4] Add more tests of cvsimport Jeff King
2009-02-20  7:40   ` Junio C Hamano
2009-02-20 11:24     ` Michael Haggerty
2009-02-20 14:12       ` [HALF A PATCH] Teach the '--exclude' option to 'diff --no-index' Johannes Schindelin
2009-02-20 14:53         ` Jeff King
2009-02-20 15:03           ` Johannes Schindelin
2009-02-20 18:34             ` Jakub Narebski
2009-02-20 20:04               ` Johannes Schindelin
2009-02-20 16:34         ` Junio C Hamano
2009-02-24 16:15           ` Johannes Schindelin
2009-02-24 17:01             ` Junio C Hamano
2009-02-20 10:21   ` [PATCH 0/4] Add more tests of cvsimport Michael Haggerty
2009-02-20 15:00     ` Jeff King
2009-02-20 21:26     ` Samuel Lucas Vaz de Mello [this message]
2009-02-21  6:32       ` Michael Haggerty
2009-02-20  8:27 ` Ferry Huberts (Pelagic)
2009-02-21 13:05   ` Michael Haggerty
2009-02-21 13:19     ` Ferry Huberts (Pelagic)
2009-02-22 16:49     ` Junio C Hamano

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=499F201E.2050106@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 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).