Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Mon, 29 Jan 2001 15:01:10 -0800
From: Bradley Bell <bradleyb@u.washington.edu>
To: Daniel Barclay <Daniel.Barclay@digitalfocus.com>
Cc: cygwin@cygwin.com
Subject: Re: Interesting words from gcc.info
Message-ID: <20010129150110.A27858@washington.edu>
References: <20010125164950.A1322@redhat.com> <3A7590CA.5A719AB4@digitalfocus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <3A7590CA.5A719AB4@digitalfocus.com>; from Daniel.Barclay@digitalfocus.com on Mon, Jan 29, 2001 at 10:48:26AM -0500

On Mon, Jan 29, 2001 at 10:48:26AM -0500, Daniel Barclay wrote:
> Christopher Faylor wrote:
> > 
> > The words below were written by Richard Stallman, I believe:
> > 
> > Reporting Bugs
> > **************
> > 
> >    Your bug reports play an essential role in making GCC reliable.
> > 
> >    When you encounter a problem, the first thing to do is to see if it
> > is already known.  *Note Trouble::.  If it isn't known, then you should
> > report the problem.
> > 
> >    Reporting a bug may help you by bringing a solution to your problem,
> > or it may not.  (If it does not, look in the service directory; see
> > *Note Service::.)  In any case, the principal function of a bug report
> > is to help the entire community by making the next version of GCC work
> > better.  Bug reports are your contribution to the maintenance of GCC.
> > 
> >    Since the maintainers are very overloaded, we cannot respond to every
> > bug report.  However, if the bug has not been fixed, we are likely to
> > send you a patch and ask you to tell us whether it works.
> > 
> > Interesting philosophy.
> 
> Any part in particular?  (I'm wondering what you're commenting on.)

That's what I was thinking.  Just wait 'till he reads the GNU Manifesto ;-)

-brad

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple