From: Scott Robert Ladd <coyote@coyotegulch.com>
To: "Downing, Thomas" <Thomas.Downing@ipc.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Copyrights: An Author's Call to Arms
Date: Fri, 02 May 2003 11:35:55 -0400 [thread overview]
Message-ID: <3EB2905B.50905@coyotegulch.com> (raw)
In-Reply-To: <170EBA504C3AD511A3FE00508BB89A9202085450@exnanycmbx4.ipc.com>
Downing, Thomas wrote:
> I could write _much_ more on this topic - but I will wait to see where
> this conversation goes first before boring/annoying LKML folks more
> than I already have.
I've probably written too much on it already -- but the topic is so
important, I think it needs to be addressed. Perhaps we need (or is
there already?) a mailing list for kernel design/philosophy?
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
next prev parent reply other threads:[~2003-05-02 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 15:19 Copyrights: An Author's Call to Arms Downing, Thomas
2003-05-02 15:35 ` Scott Robert Ladd [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 13:34 Scott Robert Ladd
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=3EB2905B.50905@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=Thomas.Downing@ipc.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;
as well as URLs for NNTP newsgroup(s).