From: Pavel@Janik.cz (Pavel Janík)
To: Larry McVoy <lm@work.bitmover.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Pavel Machek <pavel@suse.cz>,
Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>,
linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Tue, 30 Apr 2002 07:36:06 +0200 [thread overview]
Message-ID: <m3wuup694p.fsf@Janik.cz> (raw)
In-Reply-To: <20020426042242.A294@toy.ucw.cz> <Pine.LNX.4.44L.0204291633010.1960-100000@imladris.surriel.com> <20020429124514.O15730@work.bitmover.com>
From: Larry McVoy <lm@bitmover.com>
Date: Mon, 29 Apr 2002 12:45:14 -0700
Larry,
> it is today. Pavel is welcome to try and do better, but he sure as
> hell isn't going to do it in his spare time. Nobody is, it's a much
> harder problem than it looks like. I really wish people would try it
> and find out. Maybe I'm wrong, in which case we can all get on to doing
> something more fun.
you are not wrong. You have your `truth'. Pavel has his one. Pavel prefers
free software and its freedom. Some people here prefer using BK instead of
using (objectively worse) similar GPLed software. They have the right to
think that and they have the right to say so.
Yes, I too think that using BK for kernel development is politically wrong
decision and in the long run it will have bad effects on free software
(generally, Linux kernel and the community specially).
Do not take it as a critique. I do not want to criticize you or your
colleges. You did a great job!
But releasing BK under free software license would be (for me) much
better. Of course, I can not force you to change the license or something
similar. You are the creator and you have the right to release your work
under license you find the best! I (or anyone else) can not tell you what
should be done. But we all can tell you our opinion.
But I do not think that having different `truth' qualifies people to be
blackholed. Sorry, but I think you are like small child...
--
Pavel Janík
Keep it simple to make it faster.
-- The Elements of Programming Style (Kernighan & Plaugher)
next prev parent reply other threads:[~2002-04-30 5:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:57 [OFF TOPIC] BK license change Larry McVoy
2002-04-21 12:12 ` Daniel Phillips
2002-04-21 16:29 ` Greg KH
2002-04-22 7:33 ` Simon Fowler
2002-04-22 21:35 ` Larry McVoy
2002-04-21 22:14 ` Daniel Phillips
2002-04-22 22:29 ` Andreas Dilger
2002-04-21 22:52 ` Daniel Phillips
2002-04-22 23:12 ` Doug Ledford
2002-04-21 23:34 ` Daniel Phillips
2002-04-22 22:22 ` Jeff Garzik
2002-04-22 22:52 ` Larry McVoy
2002-04-25 15:01 ` Pavel Machek
2002-04-27 9:30 ` Florian Weimer
2002-04-27 13:45 ` Mr. James W. Laferriere
2002-04-27 20:34 ` Larry McVoy
2002-04-26 4:22 ` Pavel Machek
2002-04-29 19:34 ` Rik van Riel
2002-04-29 19:45 ` Larry McVoy
2002-04-30 5:36 ` Pavel Janík [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-27 18:13 Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50 ` Martin Dalecki
2002-04-28 16:55 ` Richard Gooch
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=m3wuup694p.fsf@Janik.cz \
--to=pavel@janik.cz \
--cc=Weimer@CERT.Uni-Stuttgart.DE \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=pavel@suse.cz \
--cc=riel@conectiva.com.br \
/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