Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Tue, 10 Sep 2002 13:37:37 -0400 (EDT)
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Spam filter (Was Re: problem report: gawk 3.1.1)
In-Reply-To: <20020910172813.GA9482@redhat.com>
Message-ID: <Pine.GSO.4.44.0209101332090.1269-100000@slinky.cs.nyu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 10 Sep 2002, Christopher Faylor wrote:

> On Tue, Sep 10, 2002 at 01:03:26PM -0400, Christopher Faylor wrote:
>
> Btw, you were right.  It wasn't the attachment.  It was the string
> "make<whitespace>$" as in "make $$$" that was hitting the spam blocker.

Wow!  Interesting.  Lots of people use '$' as the prompt, and 'make' is
usually part of the build instructions (though often not as verbose as in
my original message)...
Interleaving the commands with text or numbering them would have fixed
this.  I'll keep that in mind for the future.  Sorry for the trouble.
Thanks!
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

It took the computational power of three Commodore 64s to fly to the moon.
It takes a 486 to run Windows 95.  Something is wrong here. -- SC sig file


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/