linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@drgw.net>
To: Larry McVoy <lm@bitmover.com>
Cc: Zehetbauer Thomas <TZ@link.topcall.co.at>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: kernel ftp ?
Date: Mon, 23 Jul 2001 11:44:33 -0500	[thread overview]
Message-ID: <20010723114433.D13085@altus.drgw.net> (raw)
In-Reply-To: <20010723083810.C7502@work.bitmover.com>; from lm@bitmover.com on Mon, Jul 23, 2001 at 08:38:10AM -0700


On Mon, Jul 23, 2001 at 08:38:10AM -0700, Larry McVoy wrote:
>
> On Mon, Jul 23, 2001 at 11:44:02AM +0200, Zehetbauer Thomas wrote:
> > [BK flame]
>
> Thomas, sorry you feel that way.  List, if you have any questions about
> our take on Thomas' statements, some of which we feel are inaccurate,
> contact me privately.

Thomas does have some valid points.

Larry, I also understand why you can't release Bitkeeper as 'free
software'.  Please understand that we, as a community of free software
developers can NOT become dependent on any non-free software.

Most of us doing development are using BK because it works better.
However, Not providing access to the source via rsync or some other less
efficient protocol with a 'free software' implementation would be more
than a bit hypocritical.

Let's please end this discussion and any bitkeeper advocacy/disadvocacy.

(I think most people would be happy to discuss this again if either BK is
released under a license that meets the debian free software guidelines,
or another 'free' implementation is developed that allows pulls and
clones.)

--
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 Shulz

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-23 16:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23  9:44 kernel ftp ? Zehetbauer Thomas
2001-07-23 15:38 ` Larry McVoy
2001-07-23 16:44   ` Troy Benjegerdes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-15 14:10 Giuliano Pochini
2001-07-16  4:22 ` Steven Hanley
2001-07-16  7:38   ` Benjamin Herrenschmidt
2001-07-16 16:54     ` Michael Schmitz
2001-07-16 18:29       ` Benjamin Herrenschmidt
2001-07-16 18:01         ` Michael Schmitz
2001-07-16 18:12           ` Larry McVoy
2001-07-16 18:38             ` Michael Schmitz
2001-07-16 18:57               ` Larry McVoy
2001-07-22 20:30                 ` Troy Benjegerdes
2001-07-22 22:15                   ` Larry McVoy
2001-07-22 23:32                     ` Lars Magne Ingebrigtsen
2001-07-23  7:07                     ` Geert Uytterhoeven
2001-07-23  9:28                       ` Timothy A. Seufert

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=20010723114433.D13085@altus.drgw.net \
    --to=hozer@drgw.net \
    --cc=TZ@link.topcall.co.at \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).