From: linux@horizon.com
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.1 -- take two] Add CRC32C chksums to crypto and lib rout
Date: 5 Feb 2004 06:36:44 -0000 [thread overview]
Message-ID: <20040205063644.24593.qmail@science.horizon.com> (raw)
> Hard to guess what the author's intent was as he left no license, but
> perhaps you're right. However, public domain works are routinely
> relicensed by publishers when they make a trivially derived work, see
> any reprint of Shakespeare or Bach.
The author's intent was that the code is too damn trivial to start
making big important legal claims about. If you are so easily impressed
that it seems like a major contribution to western literature[*], you can
sprinkle it with copyrighted holy penguin pee and add an appropriate
consecration notice. (I.e. make trivial changes and assert copyright
over the changes.)
The disclaimer is not an attempt at a contract, but was intended as a
simple reminder of facts that should be obvious anyway. If you think it's
pointless, feel free to delete it. That's what "public domain" means.
It was inspired by distant memories of the very worthwhile InterSlip
license agreement, http://www.outercon.com/interslip.html
(I had a nice conversation with the lawyer that wrote it many years ago,
and she wanted to show that something could be funny and legally binding
at the same time.)
If MODULE_LICENSE can't cope with "Public domain", the that seems
to be a bug in MODULE_LICENSE, not grounds for a legalese workaround.
But whatever.
[*] You won't be completely alone; some people seem to think that <errno.h>
has significant artistic merit, but personally I'm afraid that sharing
that opinion would spread some horrible disease.
reply other threads:[~2004-02-05 6:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040205063644.24593.qmail@science.horizon.com \
--to=linux@horizon.com \
--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
all inboxes | Powered by JetHome®