From: "D. Stimits" <stimits@idcomm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Important, but please don't reply on the list.
Date: Mon, 17 Sep 2001 14:12:47 -0600 [thread overview]
Message-ID: <3BA6593F.94DC371E@idcomm.com> (raw)
I thought these were incredibly important, as it might have a
devastating effect on U.S. Linux developers if it ever passed. But
please don't add more comments on it to this list, instead point it out
to your local area Linux users. Here are some links on an effort to ban
all computer systems that don't pass a government security
certification:
http://slashdot.org/articles/01/09/08/0238200.shtml
http://www.wired.com/news/politics/0,1283,46655,00.html
http://www.wired.com/news/politics/0,1283,46671,00.html
I'm sorry if this isn't directly "development", but article will explain
that in the long run, developers would be devastated if the proposed
legal changes take place.
D. Stimits, stimits@idcomm.com
reply other threads:[~2001-09-17 20:10 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=3BA6593F.94DC371E@idcomm.com \
--to=stimits@idcomm.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