public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: Paul Jakma <paul@clubi.ie>
Cc: jmerkey <jmerkey@utah-nac.org>, linux-kernel@vger.kernel.org
Subject: Re: [OT] New Anti-Terrorism Law makes "hacking" punishable by life in prison
Date: Fri, 01 Jul 2005 21:13:59 -0500	[thread overview]
Message-ID: <42C5F867.2060706@linuxwireless.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0507020336180.31084@sheen.jakma.org>

Paul Jakma wrote:

> On Fri, 1 Jul 2005, Alejandro Bonilla wrote:
>
>> spam. And I can't believe, "agencies" are contacting you for this 
>> thread for the last 4 years... If they are, REALLY ask for the thread 
>> to be removed or something like that.
>
>
> http://lwn.net/Articles/140157/

Nice URL. It made my night. Is funny.

It definitely looks like someone needs a clean start. Leave the pride 
back and start all over. After all, if one stops or starts to help in 
Linux, nobody cares.

Jeff,

    I'm not aware of your "issues" or "rights", but it really looks like 
you should drop whatever you have in hands. It's not worth to battle.

.....

    The topic of this email is missleading, the "hacking" done in the 
Linux Kernel, is not the "hacking" that is punishable with prison.

    I hope this topic drops. Sorry for mentioning about it. I had no 
idea on what this was about cause I have only been reading LKML for a year.

.Alejandro

  reply	other threads:[~2005-07-02  3:14 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02  0:07 [OT] New Anti-Terrorism Law makes "hacking" punishable by life in prison jmerkey
2005-07-02  0:59 ` Alejandro Bonilla
2005-07-02  1:43   ` jmerkey
2005-07-02  3:53     ` randy_dunlap
2005-07-02 13:26     ` Jesper Juhl
2005-07-02 14:58       ` jmerkey
2005-07-02  2:39   ` Paul Jakma
2005-07-02  2:13     ` Alejandro Bonilla [this message]
2005-07-02 13:15 ` Jesper Juhl
2005-07-02 15:46 ` Kurt Wall
  -- strict thread matches above, loose matches on Subject: below --
2001-09-25 11:17 Nicholas Berry
2001-09-27  0:45 ` Dr. Kelsey Hudson
2001-09-24 23:22 Paul G. Allen
2001-09-24 23:35 ` Alan Cox
2001-09-25  0:34   ` Michael Rothwell
2001-09-25  0:40     ` Dan Hollis
2001-09-27 14:21       ` Pavel Machek
2001-09-26 11:48   ` Luigi Genoni
2001-09-24 23:37 ` Rik van Riel
2001-09-25  1:29   ` Jeff V. Merkey
2001-09-25  0:44     ` Crutcher Dunnavant
2001-09-25  0:52       ` David S. Miller
2001-09-25  1:32     ` Rik van Riel
2001-09-27 14:23     ` Pavel Machek
2001-09-30 21:16       ` M. Edward Borasky
2001-09-30 21:41         ` J Sloan
2001-09-30 22:40           ` M. Edward Borasky
2001-09-30 23:12             ` J Sloan
2001-10-01  1:15             ` Gerhard Mack
2001-10-01  1:29             ` Jan Harkes
2001-09-30 22:03         ` Alexander Viro
2001-09-30 22:57         ` John Gluck
2001-09-30 23:32           ` D. Stimits
2001-10-01  8:47         ` Helge Hafting
2001-10-01 10:41           ` Manfred Bartz
2001-10-01 12:27             ` John Jasen
2001-10-01 12:54               ` Ookhoi
2001-10-01  9:28         ` Bernd Petrovitsch
2001-10-01 12:00         ` Daniel Phillips
2001-10-02  9:40         ` Vojtech Pavlik
2001-09-27 14:18 ` Pavel Machek

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=42C5F867.2060706@linuxwireless.org \
    --to=abonilla@linuxwireless.org \
    --cc=jmerkey@utah-nac.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    /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