From: Hans Reiser <reiser@namesys.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Reiser{3,4}: problem with the copyright statement
Date: Fri, 12 Nov 2004 11:33:54 -0800 [thread overview]
Message-ID: <41951022.50207@namesys.com> (raw)
In-Reply-To: <20041112171323.GA7772@infradead.org>
Please understand it as the emphasis is on don't obscure and distort my
definition in my labeling of the code of what I have copyrights to. I
believe that for that reason, a court would allow it. I could be
wrong. That is why I ask everyone I detect for a copyright assignment,
still to this day. I don't 100% trust the code acceptance process to
guarantee that I will catch everyone....
In a world with SCOs, we need to be over careful not under careful about
such things.
Hans
Christoph Hellwig wrote:
>
>I can only say what happened to me a few years ago.
>
>
>
>
>
next prev parent reply other threads:[~2004-11-12 19:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 9:23 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:09 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:11 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:24 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:45 ` 2.6.10-rc1-mm5 Brice Goglin
2004-11-11 11:00 ` 2.6.10-rc1-mm5 Stefano Rivoir
2004-11-11 11:13 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 11:04 ` 2.6.10-rc1-mm5 Markus Trippelsdorf
2004-11-11 11:08 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 21:55 ` 2.6.10-rc1-mm5 Martin J. Bligh
2004-11-11 22:14 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 9:27 ` 2.6.10-rc1-mm5 Jens Axboe
2004-11-11 22:41 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 10:50 ` [PATCH] Fix SHMEM options David Howells
2004-11-12 16:45 ` Christoph Hellwig
2004-11-11 12:11 ` 2.6.10-rc1-mm5: yenta_socket issue Rafael J. Wysocki
2004-11-11 12:21 ` Andrew Morton
2004-11-11 12:43 ` Rafael J. Wysocki
2004-11-12 3:55 ` Rusty Russell
2004-11-11 16:50 ` 2.6.10-rc1-mm5: REISER4_LARGE_KEY is still selectable Adrian Bunk
2004-11-12 7:07 ` Vladimir Saveliev
2004-11-12 13:23 ` Adrian Bunk
2004-11-12 16:16 ` DaMouse
2004-11-12 16:37 ` Vladimir Saveliev
2004-11-12 17:15 ` Adrian Bunk
2004-12-11 17:25 ` Hans Reiser
2004-11-11 21:45 ` Reiser{3,4}: problem with the copyright statement Adrian Bunk
2004-11-11 21:59 ` Linus Torvalds
2004-11-12 16:47 ` Christoph Hellwig
2004-11-12 17:06 ` Christoph Hellwig
2004-11-12 17:11 ` Adrian Bunk
2004-11-12 17:13 ` Christoph Hellwig
2004-11-12 19:33 ` Hans Reiser [this message]
2004-11-11 22:51 ` Stephen Pollei
2004-11-12 2:08 ` Zan Lynx
2004-11-11 23:28 ` 2.6.10-rc1-mm5: reiser4: print_clog in debug.c useless? Adrian Bunk
2004-11-12 2:39 ` 2.6.10-rc1-mm5: strange fs/reiser4/linux-5_reiser4_syscall.patch Adrian Bunk
2004-11-12 14:30 ` [patch] 2.6.10-rc1-mm5: some reiser4 cleanups Adrian Bunk
2004-11-12 19:00 ` 2.6.10-rc1-mm5 Alexander Nyberg
2004-11-13 0:11 ` 2.6.10-rc1-mm5 Greg KH
2004-11-13 17:55 ` 2.6.10-rc1-mm5 [u] Martin Schlemmer [c]
2004-11-13 21:16 ` Martin Schlemmer [c]
2004-11-13 21:22 ` Andrew Morton
2004-11-13 22:19 ` Jedi/Sector One
2004-11-13 22:22 ` Martin Schlemmer [c]
2004-11-13 23:24 ` Andrew Morton
2004-11-14 0:07 ` Martin Schlemmer [c]
2004-11-14 9:10 ` Jamie Lokier
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=41951022.50207@namesys.com \
--to=reiser@namesys.com \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome