All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Larry McVoy <lm@bitmover.com>
Cc: rms@gnu.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bitkeeper
Date: 18 Jul 2003 17:58:39 -0400	[thread overview]
Message-ID: <1058565518.2479.37.camel@aurora.localdomain> (raw)
In-Reply-To: <20030718210353.GB658@work.bitmover.com>

On Fri, 2003-07-18 at 17:03, Larry McVoy wrote:
> > McVoy, changing the protocol would be extremely stupid.  
> 
> There are problems with the current protocol which can't be fixed without
> a protocol rev, problems that many of the kernel developers have asked us
> to fix.  Sooner or later we are going to fix them and then there will be
> a protocol rev.  It's possible we might do one for legal reasons but I
> doubt it.  I was just pointing out to Rory that if he insisted on doing
> something in direct violation of our license it wouldn't do him any good
> in the long run.
> 

Ah, sorry.  I was meaning the Microsoft kind of switching is stupid. 
You have tech reasons, great do them.  Mr. McVoy, sorry about my blanket
statement.  You obviously weren't just acting the way I thought you
were.

> > McVoy, thank you for helping Linus, Cox, Miller et al scale better.  As
> 
> My pleasure.  At least that part of all of this has worked out pretty
> well.  We still think BK is nowhere near good enough, there is a lot left
> to be done.  I just spent the day with one of the MySQL founders talking
> about tools for doing reviews, I think those could help.  It might be very
> cool, for example, if there was a way to distribute the review process
> and have everyone looking over code, recording notes about possible
> problems, etc.  Then Dave could grab an espresso, hit the web site,
> look over the code he cares about, see the reviews, fix it, move on.
> It's sort of "attach the bug report directly to the code" rather than
> have a bug report.  Don't know if it will work or not but we may try it.
> Stuff like that is potentially useful and part of the reason we think
> we're nowhere near done.  

Now that is a fantastic idea, kind of like cvs meets bugzilla in one
product.  I hope you are able to do it.

Anyway, please, everyone either take it private with me, or leave me out
of it.  At this point everyone knows how I feel about the issue and why
I do.  All of these arguments only seem to reinforce those feelings and
thoughts.

RMS thank you for the good you do.  Linus and all, thank you VERY much
for all the good you do.  Larry, thank you for your kind response.

Good day to you all.

Trever
--
"In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away." --
RFC1925: The Twelve Networking Truths


  reply	other threads:[~2003-07-18 21:46 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 19:51 Bitkeeper Richard Stallman
2003-07-18 20:06 ` Bitkeeper Rik van Riel
2003-07-18 20:22   ` Bitkeeper nick
2003-07-18 20:40     ` Bitkeeper Shawn
2003-07-18 21:28     ` Bitkeeper Alan Cox
2003-07-19 23:45       ` Bitkeeper Pavel Machek
2003-07-20  0:23         ` Bitkeeper Jeff Garzik
2003-07-18 20:32   ` Bitkeeper Shawn
2003-07-18 20:44     ` Bitkeeper Rik van Riel
2003-07-19 18:42     ` Bitkeeper Jan-Benedict Glaw
2003-07-19 18:49       ` Bitkeeper Larry McVoy
2003-07-19 18:57         ` Bitkeeper Jan-Benedict Glaw
2003-07-19 19:05           ` Bitkeeper Larry McVoy
2003-07-19 20:02             ` Bitkeeper Jan-Benedict Glaw
2003-07-18 20:09 ` Bitkeeper Trever L. Adams
2003-07-18 20:44   ` Bitkeeper Shawn
2003-07-18 21:03   ` Bitkeeper Larry McVoy
2003-07-18 21:58     ` Trever L. Adams [this message]
2003-07-18 22:17   ` Bitkeeper Mike Fedyk
2003-07-18 22:39     ` Bitkeeper Alan Cox
2003-07-19  8:20       ` Bitkeeper Eric W. Biederman
2003-07-19 15:34         ` Bitkeeper Mark Mielke
2003-07-18 22:29   ` Bitkeeper Scott Robert Ladd
2003-07-18 20:30 ` Bitkeeper Michael Buesch
2003-07-18 20:36   ` Bitkeeper Shawn
2003-07-18 20:44 ` Bitkeeper Larry McVoy
2003-07-18 21:03   ` Bitkeeper Shawn
2003-07-18 21:08   ` Bitkeeper David Schwartz
2003-07-18 21:28     ` Bitkeeper Shawn
2003-07-18 21:23   ` Bitkeeper Alan Cox
2003-07-18 21:50     ` Bitkeeper David Lang
2003-07-18 21:54     ` Bitkeeper Valdis.Kletnieks
2003-07-18 22:16       ` Bitkeeper Alan Cox
2003-07-18 22:01     ` Bitkeeper Trever L. Adams
2003-07-18 22:27     ` Bitkeeper Larry McVoy
2003-07-19  9:45       ` Bitkeeper Marcus Metzler
2003-07-19 20:42       ` Bitkeeper Adrian Bunk
2003-07-19 21:57         ` Bitkeeper Larry McVoy
2003-07-19 22:28           ` Bitkeeper Adrian Bunk
2003-07-19 22:39             ` Bitkeeper Larry McVoy
2003-07-19 23:45               ` Bitkeeper Adrian Bunk
2003-07-20  0:02                 ` Bitkeeper Larry McVoy
2003-07-20  0:10                   ` Bitkeeper Tupshin Harper
2003-07-20  0:26                     ` Bitkeeper Valdis.Kletnieks
2003-07-20  1:11                       ` Bitkeeper Jeff Garzik
2003-07-20  0:23                   ` Bitkeeper Jeff Garzik
2003-07-20  0:28                   ` Bitkeeper jiho
2003-07-20  0:30                   ` Bitkeeper Valdis.Kletnieks
2003-07-20  0:50                     ` Bitkeeper Larry McVoy
2003-07-20  0:22                 ` Bitkeeper Jeff Garzik
     [not found]               ` <3F19DA04.80809@c-zone.net>
     [not found]                 ` <20030719235526.GA31428@work.bitmover.com>
2003-07-20  0:21                   ` Bitkeeper jiho
2003-07-19 23:57       ` Bitkeeper Pavel Machek
2003-07-18 21:06 ` Bitkeeper Jörn Engel
2003-07-18 22:00   ` Bitkeeper Svein Ove Aas
2003-07-18 22:25     ` BK is not heaven, sure [Was: Re: Bitkeeper] J.A. Magallon
2003-07-18 23:50 ` Bitkeeper James Simmons
2003-07-19  1:05   ` offtopic crap (was Re: Bitkeeper) David S. Miller
2003-07-19 15:00     ` Jeff Garzik
2003-07-20  2:50 ` Bitkeeper Zack Brown
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07 16:23 BitKeeper Amit Vijairania
2006-03-07 17:51 ` BitKeeper Yoanis Gil Delgado
2006-03-07 17:08   ` BitKeeper Amit Vijairania
2006-03-07 18:15     ` BitKeeper Yoanis Gil Delgado
2006-03-07 18:33       ` BitKeeper Hans Reiser
2006-03-07 18:31   ` BitKeeper Hans Reiser
2006-03-07 22:27     ` BitKeeper Peter van Hardenberg
2005-04-07 22:03 Bitkeeper Paul Dorman
2005-04-07 22:18 ` Bitkeeper Jacob Gorm Hansen
2005-04-07 23:26   ` Bitkeeper Tupshin Harper
2005-04-07 23:53     ` Bitkeeper Jacob Gorm Hansen
2005-04-07 23:55     ` Bitkeeper Scott Parish
2005-04-08  0:21       ` Bitkeeper Jacob Gorm Hansen
2005-04-08  0:21         ` Bitkeeper Scott Parish
2005-04-08  6:55         ` Bitkeeper Chris Wright
2005-04-10 15:34         ` Bitkeeper Sean Perry
2005-04-11  6:54           ` Bitkeeper Jacob Gorm Hansen
2005-04-12  0:21             ` Bitkeeper David Hopwood
2004-08-16 22:21 Bitkeeper Brown, Len
2004-08-16 21:43 Bitkeeper Nathan Bryant
2003-07-19 16:00 Bitkeeper John Bradford
2003-07-19 16:17 ` Bitkeeper Mark Mielke
2003-07-19 10:33 Bitkeeper John Bradford
2003-02-15  8:21 BitKeeper John Bradford
2003-02-15 22:26 ` BitKeeper Pavel Machek
2003-02-16 11:40   ` BitKeeper John Bradford
2002-10-14 15:11 bitkeeper Cameron, Steve
2002-10-14 15:14 ` bitkeeper Cort Dougan
2002-10-14 15:25 ` bitkeeper Hollis Blanchard
2002-10-15  8:45   ` bitkeeper fred
2002-10-15  9:47     ` bitkeeper Kenneth Johansson

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=1058565518.2479.37.camel@aurora.localdomain \
    --to=tadams-lists@myrealbox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=rms@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.