DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=bQB
	zsBxp9ImKPjsUiBdL3kcjhTLwpVqFFGzaHUaAuxOCwEQ8hsOojQuqyQ5pjPKfv/H
	Tl20M1yK+Yzjs0/2Ufc16W+K+3OUaxJiEMflfLpCgXWw5dZ1COTbOAc6xA41gX9h
	J+ax/mLLtzJvpvcI5b4ylwmH3KvFKqsl9CmbTAks=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Nellis, Kenneth (Conduent)" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Please report this problem to the public mailing list...
Date: Tue, 24 Jan 2017 15:21:51 +0000
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBDC825@USA7109MB022.na.xerox.net>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

We have received several postings of people responding to the Cygwin-generated 
message: WARNING: ... Please report this problem to the public mailing list
cygwin@cygwin.com.

I wonder how many places such messages are present in the Cygwin code.

Just throwing out an idea here to help people help themselves...

Consider all such messages carrying an error code and referred to a Cygwin web 
page that contained links to separate pages for each error code, and those pages, 
then, would contain the latest information as to how to recover from the 
respective errors.

--Ken Nellis

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple