All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bitkeeper
Date: Sat, 19 Jul 2003 11:34:23 -0400	[thread overview]
Message-ID: <20030719153423.GA17587@mark.mielke.cc> (raw)
In-Reply-To: <m1lluvx700.fsf@frodo.biederman.org>

On Sat, Jul 19, 2003 at 02:20:31AM -0600, Eric W. Biederman wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > > I don't think Alan is using BK.  I could be wrong though.
> > I'm not - and with the snapshots neither I or anyone else is forced to.
> For the linux kernel.  The problem is the satellite projects which
> adopt bitkeeper less carefully.  Unless there is a general gateway I
> have missed.

They do not provide snapshots?

As long as tar files are distributed for each minor release, there is no
true 'lock in'. If you need a gateway for a specific satellite project,
there are people that could probably hook you up with the software required,
and if there are other people in your situation, one of them probably has
enough CPU + network + disk resources to host it.

The Bit Keeper issue is entirely a philosophical one. I understand
that Linus chooses to use it, because it allows him to be more
efficient. Alan Cox chooses not to use it (I'm not clear on his
reasons, but I assume they are just as good). What more proof do we
need that Bit Keeper is not locking people in?

I don't use it, and have never used it at this point, primarily
because I happen to be in the source management field currently, and I
have chosen to respect Larry's license. I'm certain that if I ever had
a proper need in terms of kernel development, the license could be
waived or altered on a case-by-case basis.

Stallman puts himself 100% in the philosopher's chair. He seems to believe
that any variation or compromise weakens his overall position. Every few
months he starts a flame war just to satisfy his own guilt that rises from
him feeling that he isn't doing enough to 'promote' free projects, even if
the free projects don't exist yet, or are not as feature-full.

A few of us have a real love-hate relationship with Stallman. We love what he
has accomplished. We hate how he accomplishes his goals.

The bottom line of all of this, is that Stallman is preaching to the wrong
people. He should stick to press releases and such. Kernel developers just
want to get work done. Any investment into writing a new source management
system would be better served by improving the linux source code. If this
wasn't so, the kernel developers wouldn't be kernel developers. They would
be like me... source management developers... :-)

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  reply	other threads:[~2003-07-19 15:19 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     ` Bitkeeper Trever L. Adams
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         ` Mark Mielke [this message]
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=20030719153423.GA17587@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.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.