From: Chris Packham <judge.packham@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "Mike.lifeguard" <mike.lifeguard@gmail.com>,
Theodore Tso <tytso@mit.edu>,
git@vger.kernel.org
Subject: Re: Pseudonymous commits
Date: Thu, 25 Mar 2010 14:30:27 -0700 [thread overview]
Message-ID: <a038bef51003251430v35ab602v661f24888d637afa@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003251605560.694@xanadu.home>
On Thu, Mar 25, 2010 at 1:14 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Thu, 25 Mar 2010, Mike.lifeguard wrote:
>
>> In the end, I managed to convince them they wouldn't be spammed (hope
>> I'm right), and I used their real emails. Nonetheless, I appreciate the
>> help.
>
> Oh, if your project is public and accessible through gitweb then
> spammers will certainly scan it and pick up their email addresses.
> Maybe some of them might even go as far as cloning Git repositories just
> for that purpose. Only local spam filtering may help in that case.
>
Sounds like it'd be a really good option to have in gitweb to
obfuscate email addresses a-la gmane and practically every other web
based mailing list/news reader. Could be fairly low hanging fruit with
a decent payoff (not that I'm volunteering). Can't do much about clone
and spam.
next prev parent reply other threads:[~2010-03-25 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 3:57 Pseudonymous commits Mike.lifeguard
2010-03-25 4:39 ` Theodore Tso
2010-03-25 4:41 ` Mike.lifeguard
2010-03-25 4:54 ` Kris Shannon
2010-03-25 5:00 ` Mike.lifeguard
2010-03-25 5:14 ` Avery Pennarun
2010-03-25 9:18 ` Alex Riesen
2010-03-25 11:05 ` Santi Béjar
2010-03-25 19:02 ` Nicolas Pitre
2010-03-25 19:26 ` Mike.lifeguard
2010-03-25 20:14 ` Nicolas Pitre
2010-03-25 21:30 ` Chris Packham [this message]
2010-03-25 23:57 ` Jakub Narebski
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=a038bef51003251430v35ab602v661f24888d637afa@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=mike.lifeguard@gmail.com \
--cc=nico@fluxnic.net \
--cc=tytso@mit.edu \
/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).