From: Martin Langhoff <martin.langhoff@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "Ævar Arnfjörð" <avarab@gmail.com>,
weigelt@metux.de, git@vger.kernel.org
Subject: Re: import determinism
Date: Sun, 7 Nov 2010 17:20:17 -0500 [thread overview]
Message-ID: <AANLkTikXxM=CfU2dKAY9khi1_tAsGDdUEc8S5AxooGH9@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2010-11-07 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 20:25 import determinism Enrico Weigelt
2010-11-07 20:46 ` Ævar Arnfjörð Bjarmason
2010-11-07 21:01 ` Andreas Schwab
2010-11-07 21:56 ` Enrico Weigelt
2010-11-07 22:20 ` Martin Langhoff [this message]
2010-11-07 22:45 ` Andreas Schwab
2010-11-09 13:43 ` Enrico Weigelt
2010-11-10 4:40 ` Martin Langhoff
2010-11-10 16:18 ` Enrico Weigelt
2010-11-10 21:25 ` Martin Langhoff
2010-11-10 22:04 ` Enrico Weigelt
2010-11-11 4:28 ` Michael Haggerty
2010-11-11 13:09 ` Enrico Weigelt
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='AANLkTikXxM=CfU2dKAY9khi1_tAsGDdUEc8S5AxooGH9@mail.gmail.com' \
--to=martin.langhoff@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=weigelt@metux.de \
/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).