From: Matthias Andree <matthias.andree@gmx.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: rmk@arm.linux.org.uk,
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 20:41:54 +0100 [thread overview]
Message-ID: <20040316194153.GA15282@merlin.emma.line.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403161132000.17272@ppc970.osdl.org>
On Tue, 16 Mar 2004, Linus Torvalds wrote:
> He does it on purpose. Apparently there is some UK law that may make it
> illegal to export other peoples email addresses without express consent,
> so rmk corrupts them with a script..
Two notes:
1.
This could be handled by only including patches of those people who
consent to their address being published,
2.
The user does not have to give a routable mail address in
BK_USER/BK_HOST, but he can set BK_HOST to whatever he wants.
If the whole corruption is intentional, then I'd suggest that RMK
participates in the maintenance of the lk-changelog.pl aka. shortlog
script. I have no chance to resolve common names through
google/lbdb/grep -r on the suspect source files unless the address is
there. There are so many people called Jonas Larsson - how do I know if
that fellow has a middle name?
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
next prev parent reply other threads:[~2004-03-16 19:48 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
[not found] ` <20040316191454.GK17813@bitmover.com>
[not found] ` <Pine.LNX.4.58.0403161132000.17272@ppc970.osdl.org>
2004-03-16 19:41 ` Matthias Andree [this message]
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=20040316194153.GA15282@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@osdl.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®