Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 30 Jan 2001 11:13:23 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Interesting words from gcc.info Message-ID: <20010130111323.B9558@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010129180857.F31725@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from vrice@solidrocksystems.com on Tue, Jan 30, 2001 at 07:06:01AM -0600 On Tue, Jan 30, 2001 at 07:06:01AM -0600, Vince Rice wrote: > No, they're not. I see four things mentioned: >1. See if the problem you have is already known (search archives, etc.). >2. If it's not known, report it. >3. The maintainers aren't bound to respond to your email. >4. If it is in fact a bug, the maintainers will make an attempt to fix it >and send you the patch to see if it works. > >This list is more like: >1. Hey, is this a bug? (meanwhile, fourteen other people last week all said >"Hey, is this a bug?") >2. The maintainers *are* bound to respond to your email -- "Hey moron, read >the FAQ, read the archives, and send us a patch!" Actually, in a fairly large percentage of cases the maintainer will respond and try to help. This is, in fact, one of the most helpful lists I've ever seen. Posting patches for cygwin fixes would not work well here since it would actually likely cause epileptic seizures in some of the "newbies", so instead we have nightly snapshots. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple