From: Hans Reiser <reiser@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: Mark Junker <mjscod@gmx.de>, reiserfs-list@namesys.com
Subject: Re: where are reiser4 sources
Date: Wed, 23 Feb 2005 09:10:50 -0800 [thread overview]
Message-ID: <421CB91A.9060302@namesys.com> (raw)
In-Reply-To: <200502221851.j1MIpPwG027166@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Tue, 22 Feb 2005 10:41:25 PST, Hans Reiser said:
>
>
>
>>That violates the license.
>>
>>
>
>Umm.. from fs/reiser4/README:
>
>Reiser4 is hereby licensed under the GNU General
>Public License version 2.
>
>Where in the GPL does it say he can't port to another OS?
>
>
He can port it to a GPL OS, not a proprietary OS.
next prev parent reply other threads:[~2005-02-23 17:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 16:16 where are reiser4 sources Mark Junker
2005-02-21 17:10 ` Sander Sweers
2005-02-21 17:59 ` Mark Junker
2005-02-22 2:08 ` David Masover
2005-02-22 15:20 ` Mark Junker
2005-02-22 18:41 ` Hans Reiser
2005-02-22 18:51 ` Valdis.Kletnieks
2005-02-23 17:10 ` Hans Reiser [this message]
2005-02-23 20:56 ` Mounting ReiserFS 3.6 RO increments journal count ? Linux Tard
2005-02-22 18:54 ` where are reiser4 sources Mark Junker
2005-02-23 17:19 ` Hans Reiser
2005-02-23 18:14 ` Mark Junker
2005-02-23 18:39 ` Rudy Zijlstra
2005-02-23 18:53 ` Hans Reiser
2005-02-23 21:06 ` Mark Junker
2005-02-23 21:03 ` Mark Junker
2005-02-24 14:46 ` Rudy Zijlstra
2005-02-25 4:34 ` David Masover
2005-02-25 8:20 ` Chester R. Hosey
2005-02-23 21:16 ` Mark Junker
2005-02-28 23:41 ` Hans Reiser
2005-02-28 21:44 ` Valdis.Kletnieks
2005-02-23 22:00 ` Jonathan Briggs
2005-02-24 0:58 ` David Masover
2005-02-22 18:56 ` Lehmann
2005-02-22 17:49 ` Hans Reiser
2005-02-22 18:29 ` Mark Junker
2005-03-02 6:29 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2005-03-01 16:52 Burnes, James
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=421CB91A.9060302@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=mjscod@gmx.de \
--cc=reiserfs-list@namesys.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 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.