From: Larry McVoy <lm@bitmover.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Larry McVoy <lm@bitmover.com>,
Tom Rini <trini@kernel.crashing.org>,
Rik van Riel <riel@conectiva.com.br>,
Christoph Hellwig <hch@caldera.de>,
hpa@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4 bitkeeper repository
Date: Fri, 22 Feb 2002 17:58:38 -0800 [thread overview]
Message-ID: <20020222175838.G11156@work.bitmover.com> (raw)
In-Reply-To: <20020222173222.E11156@work.bitmover.com> <Pine.LNX.4.44.0202221744290.1484-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.44.0202221744290.1484-100000@blue1.dev.mcafeelabs.com>; from davidel@xmailserver.org on Fri, Feb 22, 2002 at 05:46:54PM -0800
On Fri, Feb 22, 2002 at 05:46:54PM -0800, Davide Libenzi wrote:
> Larry, i've a question for you.
> Does BK use the same basic algos of diff+patch ?
Absolutely not.
> Or, if CVS fails a merge, what is the probability that BK will succeed on
> the same op ?
About 95% in our source base. You can actually run a script over the
tree, and retry all the merges with the CVS alg and the BK alg. The BK
alg automerges about 95% of the ones where CVS would not (could not).
These results are typical, in fact, the percentages go up as the number
of parallel developers go up.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2002-02-23 1:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 15:06 Linux 2.4 bitkeeper repository Christoph Hellwig
2002-02-22 15:13 ` Jeff Garzik
2002-02-22 15:26 ` DevilKin
2002-02-22 15:40 ` Jeff Garzik
2002-02-22 15:44 ` Stelian Pop
2002-02-22 16:36 ` Marcelo Tosatti
2002-02-22 18:42 ` Larry McVoy
2002-02-22 19:37 ` Rik van Riel
2002-02-22 19:45 ` Larry McVoy
2002-02-23 19:40 ` Linus Torvalds
2002-02-22 16:53 ` Larry McVoy
2002-02-22 19:26 ` Rik van Riel
2002-02-22 19:37 ` Tom Rini
2002-02-22 19:49 ` Rik van Riel
2002-02-23 0:35 ` Tom Rini
2002-02-23 1:32 ` Larry McVoy
2002-02-23 1:46 ` Davide Libenzi
2002-02-23 1:58 ` Larry McVoy [this message]
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=20020222175838.G11156@work.bitmover.com \
--to=lm@bitmover.com \
--cc=davidel@xmailserver.org \
--cc=hch@caldera.de \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=trini@kernel.crashing.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