From: Larry McVoy <lm@bitmover.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Larry McVoy <lm@bitmover.com>,
Rik van Riel <riel@conectiva.com.br>,
"Jonathan A. George" <JGeorge@greshamstorage.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel SCM: When does CVS fall down where it REALLY matters?
Date: Mon, 11 Mar 2002 09:25:38 -0800 [thread overview]
Message-ID: <20020311092538.U26447@work.bitmover.com> (raw)
In-Reply-To: <20020311090512.N26447@work.bitmover.com> <Pine.LNX.4.33L2.0203110911530.3326-100000@dragon.pdx.osdl.net>
In-Reply-To: <Pine.LNX.4.33L2.0203110911530.3326-100000@dragon.pdx.osdl.net>; from rddunlap@osdl.org on Mon, Mar 11, 2002 at 09:12:31AM -0800
On Mon, Mar 11, 2002 at 09:12:31AM -0800, Randy.Dunlap wrote:
> On Mon, 11 Mar 2002, Larry McVoy wrote:
>
> | On Thu, Mar 07, 2002 at 08:59:47PM -0300, Rik van Riel wrote:
> | > 3) graphical 2-way merging tool like bitkeeper has
> | > (this might not seem essential to people who have
> | > never used it, but it has saved me many many hours)
> |
> | I haven't verified this, but I suspect what Rik is using is the 3-way
> | file merge. If it looks like
> |
> | http://www.bitkeeper.com/newmerge.gif
> |
> | that's a 3 way file merge, the 2 big side by side windows are showing
> | you 3 diffs, the diff from the ancestor to the local version in the left
> | window, the diff from the ancestor to the remote version in the right
> | window, and then side by side diffs in that they are lined up.
> |
> | If Rik is using the 2 way file merge and likes that, he's in for a quantum
> | leap in productivity, commercial customers have reported as much as an
> | 18:1 productivity increase from the 3 way file merge.
>
> Just curious, how is this productivity increase measured?
They redid the same really nasty merge with the old tools, with Sun's
file merge, and the new filemerge. It was a bit more than 18x faster
with the new file merge.
This same customer site, which hacks the kernel by the way, claims that
well over 90% of their BK usage is spent merging, so the productivity
gains in merging are translated almost 1:1 into wall clock gains.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-03-11 17:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 23:51 Kernel SCM: When does CVS fall down where it REALLY matters? Jonathan A. George
2002-03-07 23:59 ` Rik van Riel
2002-03-08 0:03 ` Cort Dougan
2002-03-09 11:17 ` Roman Zippel
2002-03-09 16:45 ` Kurt Roeckx
2002-03-08 0:26 ` Andrew Morton
2002-03-08 0:36 ` Rik van Riel
2002-03-08 1:48 ` Neil Brown
2002-03-10 20:27 ` Pavel Machek
2002-03-11 21:11 ` Rik van Riel
2002-03-12 16:31 ` Pavel Machek
2002-03-08 7:37 ` Alex Riesen
2002-03-08 0:29 ` Jonathan A. George
2002-03-08 0:43 ` Rik van Riel
2002-03-08 9:32 ` Pau Aliagas
2002-03-08 16:37 ` Rik van Riel
2002-03-08 20:15 ` Pau Aliagas
2002-03-08 20:22 ` Rik van Riel
2002-03-08 20:28 ` Pau Aliagas
2002-03-08 0:38 ` Erik Andersen
2002-03-08 9:38 ` Pau Aliagas
2002-03-09 1:52 ` Val Henson
2002-03-09 2:00 ` Mike Fedyk
2002-03-09 2:25 ` Dave Jones
2002-03-08 1:19 ` Dave Jones
2002-03-08 20:27 ` Jonathan A. George
2002-03-08 21:59 ` Eli
2002-03-08 3:15 ` H. Peter Anvin
2002-03-08 9:39 ` Pau Aliagas
2002-03-11 17:05 ` Larry McVoy
2002-03-11 17:12 ` Randy.Dunlap
2002-03-11 17:25 ` Larry McVoy [this message]
2002-03-11 17:53 ` Jonathan A. George
2002-03-11 18:03 ` Larry McVoy
2002-03-11 20:36 ` Rik van Riel
2002-03-11 21:01 ` Larry McVoy
2002-03-11 21:28 ` Rik van Riel
2002-03-10 19:28 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 22:22 Tom Lord
2002-03-11 17:10 ` Larry McVoy
2002-03-12 6:09 ` Tom Lord
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=20020311092538.U26447@work.bitmover.com \
--to=lm@bitmover.com \
--cc=JGeorge@greshamstorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=riel@conectiva.com.br \
/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