public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS Bug Fixes 3 of 6 (Please apply all 6)
Date: Wed, 10 Apr 2002 21:21:49 +0200	[thread overview]
Message-ID: <87wuvfxstu.fsf@CERT.Uni-Stuttgart.DE> (raw)
In-Reply-To: <200204052027.g35KRc002869@bitshadow.namesys.com> <Pine.LNX.4.33.0204051347500.1746-100000@penguin.transmeta.com> <20020405171001.C6087@work.bitmover.com> <3CAEE365.4020301@namesys.com>

Hans Reiser <reiser@namesys.com> writes:

> Another model you might consider, one which would probably make you
> more money, make us happier, and better avoid "freeloaders", would be
> to make bitkeeper free for use with free software only.  This would be
> rather similar to what I use for reiserfs, which is free for use with
> free operating systems only,

Really?  I thought ReiserFS was released under the GPL.  Is this no
longer the case?

-- 
Florian Weimer 	                  Weimer@CERT.Uni-Stuttgart.DE
University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT                          +49-711-685-5973/fax +49-711-685-5898

  parent reply	other threads:[~2002-04-10 19:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 20:27 ReiserFS Bug Fixes 3 of 6 (Please apply all 6) Hans Reiser
2002-04-05 21:48 ` Linus Torvalds
2002-04-06  1:10   ` Larry McVoy
2002-04-06 12:00     ` Hans Reiser
2002-04-06 17:01       ` Larry McVoy
2002-04-06 18:11         ` [reiserfs-dev] " Oleg Drokin
2002-04-07 10:04         ` Hans Reiser
2002-04-10 19:21       ` Florian Weimer [this message]
2002-04-10 19:34         ` James Simmons
2002-04-10 19:55           ` Florian Weimer
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 21:18 Torrey Hoffman
2002-04-10 21:28 ` Florian Weimer
2002-04-13 20:03   ` Alan Cox

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=87wuvfxstu.fsf@CERT.Uni-Stuttgart.DE \
    --to=weimer@cert.uni-stuttgart.de \
    --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