From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Sun, 07 Nov 2010 22:20:17 GMT
Subject: Re: import determinism
Message-ID: <AANLkTikXxM=CfU2dKAY9khi1_tAsGDdUEc8S5AxooGH9@mail.gmail.com>
In-Reply-To: <m2lj54u9uj.fsf@igel.home>

On Sun, Nov 7, 2010 at 4:01 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> The committer info in every commit will be the same as the author info,
> so the repository conversion is completely deterministic.

For cvsimport, it is not deterministic. Given cvs'
ambiguous/buggy/inconsistent internal semantics around some
operations, cvsps makes educated guesses about what happened.

Later commits can affect those educated guesses.

IIRC, this affects the exact tree at the birth of a branch, and files
added on a branch (instead of on HEAD).

If you use cvsimport in 'incremental' runs you won't have this
problem. Whatever it decided to do, sticks.

I haven't worked in detail with Keith Packard's parsecvs but I assume
it has similar issues.

hth,


m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff