From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24766 invoked by alias); 13 Jul 2006 17:01:45 -0000 Received: (qmail 24637 invoked by uid 22791); 13 Jul 2006 17:01:44 -0000 X-Spam-Check-By: sourceware.org Received: from pool-71-248-179-44.bstnma.fios.verizon.net (HELO cgf.cx) (71.248.179.44) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Jul 2006 17:01:42 +0000 Received: by cgf.cx (Postfix, from userid 201) id 78D4B13C020; Thu, 13 Jul 2006 13:01:40 -0400 (EDT) Date: Thu, 13 Jul 2006 17:01:00 -0000 From: Christopher Faylor To: cygwin-talk@cygwin.com Subject: spotting cygwin ml trends Message-ID: <20060713170140.GA6736@trixie.casa.cgf.cx> Reply-To: cygwin-talk@cygwin.com Mail-Followup-To: cygwin-talk@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Cygwin-Talk Maiming List X-SW-Source: 2006-q3/txt/msg00023.txt.bz2 It seems like this type of email is on the rise: " is since I last updated Cygwin." "Oh, I found the problem. I had previously done . When I reverted that, things started working fine." I wonder if that's a sign of anything. It might mean that there is an increase in people/organizations using cygwin and they are including stupid instructions to work around real or imagined problems. cgf