linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: snogglethorpe@gmail.com, miles@gnu.org
Cc: Adrian Bunk <bunk@stusta.de>, Domen Puncer <domen@coderock.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: [patch] maintainers: remove moderated arm list
Date: Tue, 4 Jan 2005 14:37:03 +0100	[thread overview]
Message-ID: <20050104133703.GF26584@harddisk-recovery.com> (raw)
In-Reply-To: <fc339e4a05010405056ce624fd@mail.gmail.com>

On Tue, Jan 04, 2005 at 10:05:20PM +0900, Miles Bader wrote:
> > It's not about sanity, it's about abiding the law (the UK Data
> > Protection Act, in this particular case). As Russell King explained in
> > this thread, there are such things as real life and politicians that
> > make privacy laws.
> 
> I've had this problem with many mailing lists not based in the UK, so
> presumably that particular stupidity doesn't apply to them.  However
> sad the case of the arm lists, I'd like to know if there are more
> basic problems involved that could explain my experience.

The Data Protection Act is the UK implementation of a European Union
directive. All EU member states (should) have similar laws.

> It sounds like it would be an excellent idea not to host lists in the
> UK though...

s/UK/EU/. Like Russell already said: so far nobody volunteered to host
all EU lists plus their administrators off shore, so we have to live
with it.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2005-01-04 13:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25 17:08 [patch] maintainers: remove moderated arm list Domen Puncer
2004-12-25 17:21 ` Russell King
2004-12-25 17:34   ` Domen Puncer
2005-01-03 17:54   ` [patch] " Adrian Bunk
2005-01-03 18:25     ` Russell King
2005-01-04 17:33       ` Adrian Bunk
2005-01-05 12:52         ` Horst von Brand
2005-01-04  8:54     ` Erik Mouw
2005-01-04  9:00       ` Christoph Hellwig
2005-01-04  9:25         ` Russell King
2005-01-04  9:33           ` Christoph Hellwig
2005-01-04 10:19             ` Russell King
2005-01-05  9:20               ` Jes Sorensen
2005-01-05 14:04                 ` Alan Cox
2005-01-06  9:20                   ` Russell King
2005-01-04 21:13             ` Lee Revell
2005-01-05  0:07               ` Alan Cox
2005-01-05  1:19                 ` Lee Revell
2005-01-04 22:03             ` Alan Cox
2005-01-04  9:08       ` Russell King
2005-01-04  9:37     ` Miles Bader
2005-01-04  9:48       ` Dave Airlie
2005-01-04 10:18       ` Erik Mouw
2005-01-04 13:05         ` Miles Bader
2005-01-04 13:37           ` Erik Mouw [this message]
2005-01-04 22:03           ` Alan Cox
2005-01-09 20:26         ` Pavel Machek
2004-12-26 16:50 ` Alan Cox

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=20050104133703.GF26584@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=bunk@stusta.de \
    --cc=domen@coderock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=snogglethorpe@gmail.com \
    /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).