public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* How should I report a critical type of Cygwin bug?
@ 2014-02-26  8:10 Shaddy Baddah
  2014-02-26 11:29 ` Corinna Vinschen
  0 siblings, 1 reply; 2+ messages in thread
From: Shaddy Baddah @ 2014-02-26  8:10 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-02-26 10:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-26  8:10 How should I report a critical type of Cygwin bug? Shaddy Baddah
2014-02-26 11:29 ` Corinna Vinschen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).