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=Zqz
	c/X4n1Ej42QCwVf4i9OaFKk7mV5ZBvQl/OzBsveICzc95lkh/DKEH//Qdd+Kq1Aj
	Tfm18R/HyWbNQBdV3Il3Q4Keb0fG7zc0COvus99E1yzDO6tG//UrjL7bb+mAmxxm
	LANT4+LEcgCab1RRPdFLaVd+1UA10LFM1dW0dFk4=
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: cygcheck outputs CRLF
Date: Thu, 23 Feb 2017 17:39:35 +0000
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBEF152@USA7109MB022.na.xerox.net>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Looked, but didn't see this addressed in the archives...
Just realized that cygcheck output contains DOS line endings forcing 
me to pipe it through d2u in certain applications. Wondering if this 
is intended or desired behavior. It is installed in /usr/bin, so I 
would expect to behave Unix-like. Given an opportunity, I would vote 
for it to use Unix line endings.

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