From: Larry McVoy <lm@bitmover.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: bert hubert <ahu@ds9a.nl>, Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org
Subject: Re: who is merlin.fit.vutbr.cz?
Date: Thu, 1 Apr 2004 09:26:23 -0800 [thread overview]
Message-ID: <20040401172623.GA25496@work.bitmover.com> (raw)
In-Reply-To: <20040401133912.GA25163@mail.shareable.org>
On Thu, Apr 01, 2004 at 02:39:12PM +0100, Jamie Lokier wrote:
> bert hubert wrote:
> > On Wed, Mar 31, 2004 at 10:31:43PM +0100, Jamie Lokier wrote:
> > > > RCU for BitKeeper trees? :-)
> > >
> > > Last I heard, RCU is patented by IBM, with permission to use it in GPL
> > > programs (maybe limited to version 2 of the GPL?), so that Linux can use it.
> >
> > This is really astonishing. It is not possible to say one thing about
> > bitkeeper without descending into a discussion on patents and licenses!
>
> No. It's an unfortunate coincidence that you mentioned RCU on a
> BitKeeper(tm) thread. A suggestion to use RCU in, say, Mozilla or
> FreeBSD would have elicited a similar response.
>
> RCU patents were mentioned numerous times in the news when RCU was
> added to the kernel. One presumes, then, that IBM was keen for it to
> be known the technique is patented, and one would be wise to tread
> carefully if intending to copy the technique as it is used in Linux,
> as you jokingly suggested.
>
> In case you misunderstood, the grandparent post was not an attack on
> BitMover. Fwiw, I'm on BitMover's side if the RCU patent is relevant,
> which it probably is not. I doubt if the patent extends beyond task
> scheduling done in a certain way, although as I said I have not read it.
BitMover could care less about RCU, please leave us out of this discussion.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2004-04-01 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 1:08 who is merlin.fit.vutbr.cz? Larry McVoy
2004-03-29 7:16 ` Denis Vlasenko
2004-03-29 13:32 ` Tomasz Rola
[not found] ` <Pine.LNX.3.96.1040329151755.5234B-100000@pioneer.space.nem esis.pl>
2004-03-29 16:01 ` Jeff Woods
2004-03-29 16:10 ` Tomasz Rola
2004-03-30 19:50 ` Pavel Machek
2004-03-31 18:20 ` bert hubert
2004-03-31 21:31 ` Jamie Lokier
2004-03-31 21:45 ` bert hubert
2004-04-01 13:39 ` Jamie Lokier
2004-04-01 17:26 ` Larry McVoy [this message]
2004-04-01 6:48 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2004-03-31 13:15 Martijn Kuipers
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=20040401172623.GA25496@work.bitmover.com \
--to=lm@bitmover.com \
--cc=ahu@ds9a.nl \
--cc=jamie@shareable.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox