Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: cygcheck as body or attachment (was RE: rsync hang .... )
Date: Thu, 23 Oct 2003 21:18:31 -0700
Message-ID: <407DF7D68DD30440B5CEB70ED234D1CF03F87188@excuswa100.americas.unity>
From: "Bakken, Luke" <Luke.Bakken@getronics.com>
To: "Peter J. Stieber" <developer@toyon.com>, <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

> > I'm just a user and follower of cygwin, but it amazes me how 
> > many people put
> > the output of
> > 
> > > cygcheck -s output:
> > 
> > or cygcheck -svr in the body of their email instead of as an 
> > attachment when
> > every stinking email has
> > 
> http://cygwin.com/problems.html
> 
> at the bottom of it and that page has
> 
> "Run cygcheck -s -v -r > cygcheck.out and include that as an
attachment in
> your report."

I've used Cygwin for several years now, and have read this mailing list
for quite some time. When I encountered the rsync problem, I searched
mailing lists as well as Google to find the solution, couldn't find a
definitive answer, and eventually found one myself that worked, so I
thought I'd post it (as many other people had reported similar problems
in the archives) in order to help.

I almost didn't email the list with this solution because I couldn't
remember whether or not to include the output of cygcheck as an
attachment or as part of the body. I looked on the mailing list webpage
on cygwin.com, and couldn't see any info, so I decided to put it in the
body. I should have looked further, but I figured it wouldn't be a big
deal. Of course, I chose the wrong way, and got flamed. I now know the
right way.

Anyway, I hope that my simple patch can help someone else in the future,
and if the additional body of my message bothered anyone, I apologize.

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