DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=weh
	9rT7ZmhK99mcd4zC962KBBGXmjSm6oivyp+lqFXSkZcQiof+bli3LH2EZX1dw0cI
	ZT4cSiGa9qvRXN+fD1tOKYcd8N8wQpDLwxXUfzZrF+Erj0mEMISfyCPRSJviffFe
	qj2n/ngtrnjb/UgXXNsBzXGVLoEo41jl+MIbvom8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <530D831B.7040702@shaddybaddah.name>
Date: Wed, 26 Feb 2014 17:00:59 +1100
From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131104 Icedove/17.0.10
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: How should I report a critical type of Cygwin bug?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Risking the wrath that I should just report the bug, I would like to
just get some advice on how to go about it.

I'm encountering a problem with a rather new Cygwin package/feature that
if reproducible, has serious consequence on the hosting Windows
platform.

My concern is that if I list the steps here, readers will blindly try
this (rather easily performed) action and break their computer.

Should I just whack on a disclaimer and report it?

-- 
Regards,
Shaddy

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