public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 and BitKeeper
Date: Fri, 15 Mar 2002 10:47:05 -0800	[thread overview]
Message-ID: <20020315104705.N29887@work.bitmover.com> (raw)
In-Reply-To: <3C90E994.2030702@candelatech.com> <20020315080408.D11940@work.bitmover.com> <a6tcnf$shg$1@penguin.transmeta.com> <3C923A6A.2030905@mandrakesoft.com> <a6teec$sis$1@penguin.transmeta.com>
In-Reply-To: <a6teec$sis$1@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Mar 15, 2002 at 06:27:24PM +0000

On Fri, Mar 15, 2002 at 06:27:24PM +0000, Linus Torvalds wrote:
> (It should be noted that this design mistake is also one of the
> stumbling blocks for ever improving the BK databases. It limits your
> viability in the long run, which is why I'm trying to prod Larry into
> fixing it).

Here's the deal.  I know you guys all think that I'm a genius and
everything, but I'm actually dumb as a board.  The "design mistake"
was made so that I could have BK generate pure SCCS files and test that
I did the same thing as a known working tool, ATT SCCS.  By doing that,
I easily saved myself a year of design.  Making interleaved deltas work
is hard for me (we have Rick here now and he's forgotten more about this
stuff than I'll ever know, but we didn't have him when I wrote the SCCS
compat weave).

At this point, I trust our implementation of the weave more than I trust
the ATT one, and ours handles several cases that theirs doesn't, so I'm
a lot less concerned about that compatibility.

And we know that we can get better performance, and dramatically reduce
fragmentation, by sticking all the files in one big file, and we've known
this for a long time.  We're gonna do it, you're gonna love, it's less
filling, it tastes great.  There is only so many things that we can do at
once and this is on our short list, but it isn't at the top.  Keep that
in mind as you push us to make enhancements, there is no free lunch, so
prioritize.

I'm gonna hack at least make & patch to know about the new format and
work the way they do now.  So I can have your cake and eat it too.
If I can't get the FSF to take the changes, we'll just ship 'em,
we ship diff & patch already, so it's not so hard to alias make='bk make'.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-03-15 18:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  4:42 Linux 2.4 and BitKeeper Marcelo Tosatti
2002-03-14  6:33 ` Ben Greear
2002-03-14  5:36   ` Marcelo Tosatti
2002-03-14  6:37   ` David S. Miller
2002-03-14  6:42   ` Larry McVoy
2002-03-14  7:54     ` Alex Riesen
2002-03-14 15:46       ` Larry McVoy
2002-03-14 18:10         ` Alex Riesen
2002-03-14 18:19     ` Ben Greear
2002-03-14 18:26       ` Robert Love
2002-03-14 18:40         ` Ben Greear
2002-03-14 22:56           ` Mark Frazer
2002-03-15 11:10     ` David Woodhouse
2002-03-15 16:04       ` Larry McVoy
2002-03-15 16:17         ` Stelian Pop
2002-03-15 17:58         ` Linus Torvalds
2002-03-15 18:16           ` Jeff Garzik
2002-03-15 18:27             ` Linus Torvalds
2002-03-15 18:47               ` Larry McVoy [this message]
2002-03-17  0:39                 ` Daniel Phillips
2002-03-17  5:42                   ` Mike Fedyk
2002-03-18 16:47               ` [PATCH] 2.5.7-pre2 IDE 22a Martin Dalecki
2002-03-15 18:39           ` Linux 2.4 and BitKeeper Larry McVoy
2002-03-15 19:01             ` Linus Torvalds
2002-03-15 19:10               ` Larry McVoy
2002-03-15 19:20                 ` Linus Torvalds
2002-03-15 19:30                   ` Larry McVoy
2002-03-16  0:31                     ` Andreas Ferber
2002-03-16  1:02                       ` Andreas Dilger
2002-03-15 16:10       ` David Woodhouse
2002-03-15  4:35 ` Stephen Torri

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=20020315104705.N29887@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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