From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Christoph Lameter <christoph@lameter.com>, linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Sat, 27 Apr 2002 23:50:16 +0200 [thread overview]
Message-ID: <3CCB1D18.2010402@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0204271425030.25240-100000@weyl.math.psu.edu>
Uz.ytkownik Alexander Viro napisa?:
>
> On Sat, 27 Apr 2002, Christoph Lameter wrote:
>
>
>>The best thing would be to stop this egg-dance around open sourceness and
>>release BK under GPL. This is wasting too much time. Trying to use a
>
>
> 1001st time, CHOICE OF LICENSE BELONGS AUTHOR OF CODE IN QUESTION, dimwit.
> How many times should that be repeated until it sinks down?
Anton please please let this discussion going on. It is *very*
good at pointing at the people who need an permanent personal
entry in my killfile for lkml ;-).
next prev parent reply other threads:[~2002-04-27 22:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 18:13 [OFF TOPIC] BK license change Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50 ` Martin Dalecki [this message]
2002-04-28 16:55 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-04-21 16:57 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
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=3CCB1D18.2010402@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.