Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Wed, 27 Mar 2002 13:58:39 -0800
From: Greg Stein <gstein@lyra.org>
To: dev@httpd.apache.org
Subject: Re: Email addresses in changes file
Message-ID: <20020327135839.D20607@lyra.org>
References: <Pine.OSX.4.43.0203270928590.25560-100000@mobile.webweaving.org>
 <Pine.GSO.4.31.0203270933430.21549-100000@garibaldi.commerce.ubc.ca>
 <20020327094248.C14500@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20020327094248.C14500@apache.org>;
 from jerenkrantz@apache.org on Wed, Mar 27, 2002 at 09:42:48AM -0800

On Wed, Mar 27, 2002 at 09:42:48AM -0800, Justin Erenkrantz wrote:
> On Wed, Mar 27, 2002 at 09:36:31AM -0800, Joshua Slive wrote:
> > On Wed, 27 Mar 2002 dirkx@covalent.net wrote:
> > > Anyone think it is a good idea if I did a
> > >
> > > 	s/@/_at_/g
> > >
> > > on the email addresses in the Changes file ?
> > 
> > -0
> > 
> > - It won't solve the problem.
> > 
> > - It looks amateurish
> 
> Yup.  -0 here as well.
> 
> As simple as our script is, lots of spiders now do the converse:
> s/_at_/@/g.  =)  The only thing would be to remove email addresses.
> 
> I think that's a good thing to have though - if we don't regularly
> accept contributions from that person, we should have a contact
> email address for them.  -- justin

"Me too!"

-0 here. If we remove it from CHANGES, then they just crawl the dev mailing
list archive. There isn't any reasonable way to avoid it, so let's not
obfuscate our materials.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/