Re: cvs-migration.txt

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Jan 16, 2006, 01:31 UTC
Message-ID: <46a038f90601151731vc72835dja390b7934a6b575f@mail.gmail.com>
In-Reply-To: <7vy81h2o3a.fsf@assigned-by-dhcp.cox.net>

On 1/16/06, Junio C Hamano <junkio@cox.net> wrote:

> what we are
> saying here is that you should never commit into these branches
> yourself and let cvsimport be the only one that touch them, so
> using commiter date and author date would not make a difference.

Exactly. You should make a new head off the one imported from cvs, and work there. This supports continued use of cvsimport if the cvs repo is still active. To bring in those changes you will have to merge them into your branch.

If you are 200% certain that the cvs repo is going to be removed immediately, you can ignore this advice. Run the cvsimport once, and then start developing on top. If you do this, however, don't run that cvsimport ever again, for it will mess up things royally ;)

But it's a bad idea to keep using the same branches in any case. Life is saner if you work on new heads.

martin