public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jmerkey <jmerkey@utah-nac.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Alejandro Bonilla <abonilla@linuxwireless.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [OT] New Anti-Terrorism Law makes "hacking" punishable by life in prison
Date: Sat, 02 Jul 2005 08:58:26 -0600	[thread overview]
Message-ID: <42C6AB92.4080609@utah-nac.org> (raw)
In-Reply-To: <9a87484905070206264efea55a@mail.gmail.com>


It's in the archives now, so the purpose is served. The sociopaths using 
the parent thread have just lost their toy.

J

Jesper Juhl wrote:

>On 7/2/05, jmerkey <jmerkey@utah-nac.org> wrote:
>  
>
>>OK.  I ask for this thread and associated posts to be removed, is this
>>is allowed.  The Provo Daily Herald and KSL Channel 5
>>news asked me questions about it.  I did not author it.
>>
>>    
>>
>[...]
>
>I'd say that that request is damn near impossible. First of all, as
>Randy has already pointet out kernel.org does not maintain email
>archives, secondly, the thread will be archived on a number of
>different sites outside kernel.org's control - there are *many* lkml
>archives on the 'net. In addition to LKML archives you'd also have to
>contact news sites that may have written articles on the thread and
>copied the message(s) in part or in full, and then there is any number
>of search engines that may have cached the thread and sites like The
>Wayback Machine that may have cached the lkml archives or the news
>sites etc etc etc... And finally you have a huge number of unknown
>people who may have kept personal LKML archives on their private
>machines going back several years - there's no way to identify those
>people and certainly no way to get them to remove a specific thread
>from their personal archives.
>Once a message is posted to a public mailing list (especially one as
>widely archived & commented on as LKML) it is practically impossible
>to get rid of - there's always going to be someone somewhere that has
>a copy.
>
>  
>


  reply	other threads:[~2005-07-02 16:26 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 [this message]
2005-07-02  2:39   ` Paul Jakma
2005-07-02  2:13     ` Alejandro Bonilla
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=42C6AB92.4080609@utah-nac.org \
    --to=jmerkey@utah-nac.org \
    --cc=abonilla@linuxwireless.org \
    --cc=jesper.juhl@gmail.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