Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Wed, 12 Mar 2003 14:53:33 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin gcc 3.4 and cygwin
Message-ID:	<Pine.GSO.4.44.0303121446300.2707-100000@eos>
MIME-Version:	1.0

Brian Ford wrote:

>Cygwin's gcc has an extensive number of patches and is pre 3.2.  There
>must be a reason for this.  Maybe it is just volunteer time, but somehow
>I doubt it.

Christopher Faylor wrote:

>There is no hidden agenda here.
>
Ok.  But is it "kosher" for me to submit and revise patches to vanilla gcc
that I did not write, ie. those that are already part of Cygwin's gcc?

>If you want to improve the trunk version of gcc, feel free to submit
>patches to the appropriate mailing list.  You do have an assignment on
>file with the FSF, right?
>

So far, all of my patches to FSF software have been classified as
"trivial" or were before the strict assignment campaign.  This is
obviously easily fixable by me when necessary, though.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -