mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: TLD.rmk.(none) junk in BitKeeper logs where BK_HOST belongs?
Date: Wed, 17 Mar 2004 11:22:49 +0100	[thread overview]
Message-ID: <20040317102249.GA6464@merlin.emma.line.org> (raw)
In-Reply-To: <1079479795.17681.6.camel@imladris.demon.co.uk>

On Tue, 16 Mar 2004, David Woodhouse wrote:

> On Tue, 2004-03-16 at 19:30 +0000, Russell King wrote:
> > and read through the (flash) bits.  Now consider "are email addresses
> > information which can be used to identify individuals?"  The answer is
> > "yes".  Are we storing that in a kind of database?  Yes.  Therefore,
> > does this fall under the terms of the Data Protection Act?  Yes.
> 
> You already have my email address in your copy of the BK tree. You
> achieve nothing by simply not adding _more_ valid email addresses.
> 
> I think civil disobedience in this case is appropriate.

Why would it? I see legal ways to provide such information - and after
all, we want the authors' names rather than their addresses in the frist
place, at least in "shortlog".

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95

  reply	other threads:[~2004-03-17 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 18:44 Matthias Andree
2004-03-16 19:30 ` Russell King
2004-03-16 23:29   ` David Woodhouse
2004-03-17 10:22     ` Matthias Andree [this message]
     [not found] ` <20040316191454.GK17813@bitmover.com>
     [not found]   ` <Pine.LNX.4.58.0403161132000.17272@ppc970.osdl.org>
2004-03-16 19:41     ` Matthias Andree
2004-03-16 19:45       ` Russell King
2004-03-16 20:44         ` Matthias Andree

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=20040317102249.GA6464@merlin.emma.line.org \
    --to=matthias.andree@gmx.de \
    --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

all inboxes | Powered by JetHome®