From: Paul Jackson <pj@sgi.com>
To: Mark Adler <madler@alumni.caltech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc 3.5 fixes
Date: Mon, 5 Jul 2004 14:44:36 -0700 [thread overview]
Message-ID: <20040705144436.62544a3d.pj@sgi.com> (raw)
In-Reply-To: <9FC7DA98-CEA3-11D8-B083-000A95820F30@alumni.caltech.edu>
I'm not a lawyer, but I don't see why you'd want the copyright notice
in the executable:
* It's probably the source text that you're intending to copyright, not
the binary executable bits.
* If you look, I believe you will find that there are almost no other
copyright strings in the vmlinux executable.
* By what right can I copy or distribute a kernel built with this string
in it? The comments in zlib.h let us use the source, but I don't see
any authorization to use the resulting executable bits on which this
static copyright string seems to assert copyright.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-07-05 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2e9is-5YT-1@gated-at.bofh.it>
[not found] ` <2e9iu-5YT-5@gated-at.bofh.it>
[not found] ` <2ecq2-80i-1@gated-at.bofh.it>
[not found] ` <7ab39013.0407042237.40ea9035@posting.google.com>
[not found] ` <20040705064010.C9BFB5F7AA@attila.bofh.it>
2004-07-05 16:51 ` Mark Adler
2004-07-05 21:44 ` Paul Jackson [this message]
2004-07-06 1:16 ` Mark Adler
2004-07-06 1:45 ` Paul Jackson
2004-07-06 3:51 ` Jesse Stockall
2004-07-06 4:43 ` Mark Adler
2004-07-06 6:11 ` bert hubert
2004-07-06 6:46 ` David Woodhouse
2004-07-06 15:02 ` Mark Adler
2004-07-04 6:58 Anton Blanchard
2004-07-04 7:01 ` Anton Blanchard
2004-07-04 7:07 ` Anton Blanchard
2004-07-04 10:24 ` Bartlomiej Zolnierkiewicz
2004-07-04 11:04 ` Anton Blanchard
2004-07-06 15:28 ` Randy.Dunlap
2004-07-11 10:23 ` Anton Blanchard
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=20040705144436.62544a3d.pj@sgi.com \
--to=pj@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madler@alumni.caltech.edu \
/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