Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 26 Nov 2002 21:23:27 -0500
From: Christopher Faylor <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: compressing cygcheck output considered harmful?
Message-ID: <20021127022327.GA27364@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.1i

As much as I like the idea of sending cygcheck output as an attachment
(Randall take a bow), I really would prefer it if people would refrain
from compressing the output when they send it.  The theory is that we
should just be able to open the attachment in our email readers and scan
for problems.  If the attachment is compressed then that is not
trivially possible.

A standard cygcheck output is around 30K.  I don't think that should be
too much of a burden for most people.

I just noticed that I put off looking at some cygcheck output all day
because it required saving and uncompressing in another directory.  I
read the cygwin mailing list in small time slices throughout the day and
I just didn't have enough time to get to this task.  Sad, I know, but
I'll bet I'm not alone.

Does it make sense not to send cygcheck output in compressed format?

cgf
--
Please do not send me personal email with cygwin questions or observations.
Use the resources at http://cygwin.com/ .

--
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/