This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Why not compress cygcheck output? (was RE: updatedb broken?)
- From: "Max Bowsher" <maxb at ukf dot net>
- To: "David Rothenberger" <daveroth at acm dot org>,<cygwin at cygwin dot com>
- Date: Fri, 23 May 2003 22:34:05 +0100
- Subject: Re: Why not compress cygcheck output? (was RE: updatedb broken?)
- References: <3ECE9227.E1A449B6@acm.org>
David Rothenberger wrote:
> Igor Pechtchanski wrote:
>> As a matter of fact, <http://cygwin.com/bugs.html> and
>> <http://cygwin.com/problems.html> should be the same document. And it
>> does say
>>
>> Run cygcheck -s -v -r > cygcheck.out and include that as an attachment
>> in your report. Please do not compress the output. Just attach it as
>> a straight text file so that it can be easily viewed.
>>
>> However, the part about it having to be an attachment is not stressed.
We
>> should probably do something about that.
>> Igor
>
> My mailer (netscape) refuses to attach text files as anything but
> inline. Yes, I know I can use another mailer, but that's kind of a pain
> and the few I've checked out also don't allow this to be controlled.
> While I'm sure there is a mailer that allows it, I can easily avoid this
> issue by compressing the cygcheck output.
>
> So, why is it important that the output not be compressed? In fact, if
> you asked for compressed output, it seems more likely that it would be
> an attachment and not inlined.
Attached because: Putting a list of every package name in lots of mails
makes searching the archives very difficult, since you tend to me swamped by
false hits.
Uncompressed because: Few people will be bothered to detach, uncompress
using an external program, and view a cygcheck. The person with the problem
needs to make it easy for someone to help them - and that means all details
viewable without leaving the mail client.
Max.
--
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/