From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: TLD.rmk.(none) junk in BitKeeper logs where BK_HOST belongs?
Date: Tue, 16 Mar 2004 19:30:14 +0000 [thread overview]
Message-ID: <20040316193014.B7886@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040316184455.GA31710@merlin.emma.line.org>; from matthias.andree@gmx.de on Tue, Mar 16, 2004 at 07:44:56PM +0100
On Tue, Mar 16, 2004 at 07:44:56PM +0100, Matthias Andree wrote:
> whose broken script or BitKeeper installation causes all these annoying
> de.rmk.(none), au.rmk.(none) and all that to be logged instead of the
> real BK_HOST?
I do it purposely. Go read:
http://www.informationcommissioner.gov.uk/
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.
Therefore I myself do not want to store peoples email addresses BK,
thereby avoiding this issue entirely.
> I don't care to know who it is but would the offending system please be
> updated or fixed?
Nope - live with it.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-03-16 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 18:44 TLD.rmk.(none) junk in BitKeeper logs where BK_HOST belongs? Matthias Andree
2004-03-16 19:30 ` Russell King [this message]
2004-03-16 23:29 ` David Woodhouse
2004-03-17 10:22 ` Matthias Andree
[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=20040316193014.B7886@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.