Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 5 May 2005 20:59:59 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin version 1.5.16-1 (exim 4.50-1, minires 1.00-1, perl 5.8.6-4) attempting to run spamassassin (spamc and spamd) Message-ID: <20050506005959.GB24007@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <427A9D72.2070302@infobro.com> <20050505232423.GG15066@trixie.casa.cgf.cx> <427ABD77.A45440E9@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427ABD77.A45440E9@dessent.net> User-Agent: Mutt/1.5.8i On Thu, May 05, 2005 at 05:42:31PM -0700, Brian Dessent wrote: >Christopher Faylor wrote: >>reported that it was still broken in the cygwin-developers mailing >>list. That's why it is only fixed in the snapshot. I'm glad to see >>that it is now ok but it makes me wonder what else I now broke. :-) > >I still have not given up on trying to come up with a decent testcase >for that, btw. Thanks. This is something that I suspect is apt to break again. It would be nice to have a way to detect that. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/