From: Oswald Buddenhagen <ossi@kde.org>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
Jon Smirl <jonsmirl@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
monotone-devel@nongnu.org, dev@cvs2svn.tigris.org
Subject: Re: cvs import
Date: Wed, 13 Sep 2006 23:15:21 +0200 [thread overview]
Message-ID: <20060913211521.GA3336@ugly.local> (raw)
In-Reply-To: <4508724D.2050701@bluegap.ch>
On Wed, Sep 13, 2006 at 11:04:13PM +0200, Markus Schiltknecht wrote:
> Martin Langhoff wrote:
> >One thing that bothers me in the cvs2svn algorithm is
> >that is not stable in its decisions about where the branching point is
> >-- run the import twice at different times and it may tell you that
> >the branching point has moved.
>
> Huh? Really? Why is that? I don't see reasons for such a thing happening
> when studying the algorithm.
>
that's certainly due to some hash being iterated. python intentionally
randomizes this to make wrong assumptions obvious.
there is actually a patch pending to improve the branch source selection
drastically. maybe this is affected as well.
> For sure the proposed dependency-resolving algorithm which does not rely
> on timestamps does not have that problem.
>
i think that's unrelated.
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
next prev parent reply other threads:[~2006-09-13 21:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45084400.1090906@bluegap.ch>
2006-09-13 19:01 ` cvs import Jon Smirl
2006-09-13 20:41 ` Martin Langhoff
2006-09-13 21:04 ` Markus Schiltknecht
2006-09-13 21:15 ` Oswald Buddenhagen [this message]
2006-09-13 21:16 ` Martin Langhoff
2006-09-14 4:17 ` Michael Haggerty
2006-09-14 4:34 ` Jon Smirl
2006-09-14 5:02 ` Michael Haggerty
2006-09-14 5:21 ` Martin Langhoff
2006-09-14 5:35 ` Michael Haggerty
2006-09-14 5:30 ` Jon Smirl
2006-09-14 4:40 ` Martin Langhoff
2006-09-13 21:05 ` Markus Schiltknecht
2006-09-13 21:38 ` Jon Smirl
2006-09-14 5:36 ` Michael Haggerty
2006-09-14 15:50 ` Shawn Pearce
2006-09-14 16:04 ` Jakub Narebski
2006-09-14 16:18 ` Shawn Pearce
2006-09-14 16:27 ` Jon Smirl
2006-09-14 17:01 ` Michael Haggerty
2006-09-14 17:08 ` Jakub Narebski
2006-09-14 17:17 ` Jon Smirl
2006-09-15 7:37 ` Markus Schiltknecht
2006-09-16 3:39 ` Shawn Pearce
2006-09-16 6:04 ` Oswald Buddenhagen
2006-09-16 6:21 ` Nathaniel Smith
2006-09-13 22:52 ` Nathaniel Smith
2006-09-13 23:21 ` Daniel Carosone
2006-09-13 23:52 ` [Monotone-devel] " Daniel Carosone
2006-09-13 23:42 ` Keith Packard
2006-09-14 0:32 ` Nathaniel Smith
2006-09-14 0:57 ` [Monotone-devel] " Jon Smirl
2006-09-14 1:53 ` Daniel Carosone
2006-09-14 2:30 ` [Monotone-devel] " Shawn Pearce
2006-09-14 3:19 ` Daniel Carosone
2006-09-14 21:57 ` [Monotone-devel] " Petr Baudis
2006-09-14 22:04 ` Shawn Pearce
2006-09-14 2:35 ` Shawn Pearce
2009-02-16 9:17 CVS import Ferry Huberts (Pelagic)
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=20060913211521.GA3336@ugly.local \
--to=ossi@kde.org \
--cc=dev@cvs2svn.tigris.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=markus@bluegap.ch \
--cc=martin.langhoff@gmail.com \
--cc=monotone-devel@nongnu.org \
/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).