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
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 11 Feb 2002 13:14:28 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bison 1.31 is broken...
Message-ID: <20020211181428.GA877@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <NCBBIHCHBLCMLBLOBONKEEFICKAA DOT g DOT r DOT vansickle AT worldnet DOT att DOT net> <002201c1b325$489aa220$6600a8c0 AT cherry>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002201c1b325$489aa220$6600a8c0@cherry>
User-Agent: Mutt/1.3.23.1i

On Mon, Feb 11, 2002 at 09:47:02AM -0800, David Gluss wrote:
>Umm, while we're on the subject of Bison, I submitted a fix for bison
>last week some time.  Any chance it will be incorporated soon, or that
>something will happen so that the current bison will be usable with
>Microsoft C?

I just build bison straight from the FSF sources.  I don't have any
desire to maintain a fork.  If you think you have a fix, then you should
send it to the FSF.

A search of the FSF site unearths this:

http://www.gnu.org/prep/mailinglists.html#34

cgf

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