linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick@snowman.net
To: Rik van Riel <riel@redhat.com>
Cc: Richard Stallman <rms@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Bitkeeper
Date: Fri, 18 Jul 2003 16:22:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0307181621530.16266-100000@ns.snowman.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307181603340.21716-100000@chimarrao.boston.redhat.com>

How about all of you take a much nicer tilt on this, and ask McVoy (who's
already giveing you the software free) his price to GPL bitkeeper.
	Nick

On Fri, 18 Jul 2003, Rik van Riel wrote:

> On Fri, 18 Jul 2003, Richard Stallman wrote:
> 
> > I think it would be appropriate at this point to write a free client
> > that talks with Bitkeeper,
> 
> Maybe.  I'll leave that decision to whomever decides to
> invest his time and/or money in implementing such software.
> 
> > and for Linux developers to start switching to that from Bitkeeper.
> 
> That would be a bit premature.  I certainly wouldn't switch
> to a piece of software that doesn't exist yet. ;)
> 
> To put it more bluntly: free software would have to implement
> a very significant amount of Bitkeeper's functionality before
> I would ever consider switching to it.
> 
> At the moment there simply is no equivalent free alternative
> to Bitkeeper, so there's nothing to switch to.  Once such an
> alternative exists we could continue this debate.
> 
> kind regards,
> 
> Rik
> -- 
> Great minds drink alike.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


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

Thread overview: 65+ 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   ` nick [this message]
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         ` 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 --
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

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=Pine.LNX.4.21.0307181621530.16266-100000@ns.snowman.net \
    --to=nick@snowman.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).