X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: MailHop Outbound by DynDNS
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18DlnyDbEvw13YJArjo6BPE
Date: Sat, 14 Apr 2012 14:46:50 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Installation / download issues
Message-ID: <20120414184650.GA17287@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20120414170056 DOT GC15801 AT ednor DOT casa DOT cgf DOT cx> <Pine DOT LNX DOT 4 DOT 33 DOT 1204141023240 DOT 15017-100000 AT denzel DOT in>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.1204141023240.15017-100000@denzel.in>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sat, Apr 14, 2012 at 11:01:57AM -0700, Richard Troy wrote:
>...During an exchange on a completely unrelated topic:
>[most of another rant snipped]
>
>As you want a bug report, I think I saved the logs, so maybe that's still
>possible, though I was under the impression that they got overwritten on
>subsequent tries; I _think_ I may have saved the logs from the first
>attempt on this latest cycle last Tuesday night. I'll try and dig into it
>tomorrow AM over coffee and if it's still available, I'll log a bug. As
>I'm not a Cygwin committer, is submitting here, on-list, sufficient, or
>where do you want me to enter it officially? "Problem reports" url cited
>below?

Obviously you are not a Cygwin committer.  I'd hope that someone with
commit privileges would be taking a proactive role in fixing bugs rather
than ranting about them.  If you are a programmer, however, then patches
are always welcome.  For setup.exe, those patches would go to the
cygwin-apps mailing list.

Otherwise, yes, of course, I'd want anyone reporting a problem to use
the guidelines at http://cygwin.com/problems.html .  That's the whole
point of having a link at the bottom of every message.

You might also pay particular attention to the link near the beginning
of that page which talks about asking smart questions.

http://www.catb.org/~esr/faqs/smart-questions.html

Specifically:

http://www.catb.org/~esr/faqs/smart-questions.html#beprecise
http://www.catb.org/~esr/faqs/smart-questions.html#symptoms
http://www.catb.org/~esr/faqs/smart-questions.html#courtesy

setup.exe has seen a lot of development in the last year so, although
there are no guarantees that anything will be fixed, it's possible that
someone might want to look into any issue that you report.

I can guarantee that there won't be any fixes whatsoever coming if the
best you can do is rant about past issues, claim that other people have
problems too, and protest your loyalty to the project.  Those are all
irrelevant to getting a problem fixed.

cgf

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