From: Troy Benjegerdes <hozer@drgw.net>
To: Dana Lacoste <dana.lacoste@peregrine.com>,
"'Larry McVoy'" <lm@bitmover.com>,
linux-kernel@vger.kernel.org
Subject: BK scales, Bitmover doesn't [was Re: BK stuff ]
Date: Thu, 27 Dec 2001 15:59:56 -0600 [thread overview]
Message-ID: <20011227155956.G25200@altus.drgw.net> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A3B@ottonexc1.ottawa.loran.com> <20011227133951.M25698@work.bitmover.com>
In-Reply-To: <20011227133951.M25698@work.bitmover.com>; from lm@bitmover.com on Thu, Dec 27, 2001 at 01:39:51PM -0800
On Thu, Dec 27, 2001 at 01:39:51PM -0800, Larry McVoy wrote:
> My apologies to the list if this is considered off topic. I changed the
> subject so you can kill this thread if you like. I know how popular BK
> discussions are :-)
(I'm quite sure this is off-topic, but oh well :-/ )
I want to make a note about something that concerns me, and I haven't
really seen discussed much..
BK is quite nice, and from it's design, could probably scale to haveing
every linux developer on the planet using the same 'base' linux kernel
tree with no problem. (Please don't argue with this point, it's not what
I'm concerned about)
However, the real problem I see is that althought Bitkeeper (the product)
scales very well, Bitmover (the company) does NOT. Bitmover needs income
to scale, and I'm worried that if BK takes off for kernel development,
the demands on Bitmover from kernel developers will far outstrip the
increase in income they get from 'commercial' developers. If this happens,
it's only going to end in everyone getting pissed off.
I can't think of any 'win/win' solutions for this, problem only
'lose/lose' ones. Is anyone else worried about this, or am I just a
pessimist?
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Schulz
next prev parent reply other threads:[~2001-12-27 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 21:24 The direction linux is taking Dana Lacoste
2001-12-27 21:39 ` BK stuff [was Re: The direction linux is taking] Larry McVoy
2001-12-27 21:59 ` Troy Benjegerdes [this message]
2001-12-27 22:23 ` BK scales, Bitmover doesn't [was Re: BK stuff ] Larry McVoy
2001-12-27 23:09 ` Troy Benjegerdes
2001-12-27 23:40 ` Larry McVoy
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=20011227155956.G25200@altus.drgw.net \
--to=hozer@drgw.net \
--cc=dana.lacoste@peregrine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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
all inboxes | Powered by JetHome®