From: Jason Molenda <jason-swarelist@molenda.com>
To: overseers@sourceware.org
Subject: Re: [My e-mail address in gcc-bugs mailing list archive]
Date: Thu, 03 Mar 2005 20:34:00 -0000 [thread overview]
Message-ID: <20050228101230.A45035@molenda.com> (raw)
In-Reply-To: <20050228180504.GJ29453@trixie.casa.cgf.cx>; from me@cgf.cx on Mon, Feb 28, 2005 at 01:05:04PM -0500
On Mon, Feb 28, 2005 at 01:05:04PM -0500, Christopher Faylor wrote:
> I wasn't exactly sure what I was implying either. I guess it was
> something like a "nomunge=1" option, the theory being that spammers
> wouldn't be following the gcc mailing list where this setting could be
> announced.
That makes good sense. Not only would they have to read the list,
but they'd have to modify their crawler-bot to add nomunge=1 followed
by an ampersand option-delimiter in the URL of the get raw message.
I don't think we're a juicy enough target for the spambot-authors to
be monitoring how sourceware is set up and modify their software
specifically for us.
FWIW, all joking aside, my main concern with munging the bodies of
messages was that patches could fail to apply if there were e-mail
addresses in comments. If we munge e-mail addresses in msg bodies
of both the mhonarc and get-raw-text (without an option like "nomunge=1")
accessor methods, people will have to modify those patches by hand.
Incidentally, I don't know if mhonarc allows for munging in
attachments, e.g. patches attached to an e-mail message.
J
prev parent reply other threads:[~2005-02-28 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 14:02 Chris Faylor
2005-03-01 14:34 ` Ian Lance Taylor
2005-03-01 14:41 ` Christopher Faylor
2005-03-02 20:07 ` Ian Lance Taylor
2005-03-03 3:11 ` Christopher Faylor
2005-03-03 3:53 ` Jason Molenda
2005-03-03 10:22 ` Christopher Faylor
2005-03-03 20:34 ` Jason Molenda [this message]
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=20050228101230.A45035@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).