Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Sat, 8 Sep 2001 23:04:05 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Want to be a gcc/binutils maintainer? Message-ID: <20010908230405.A17395@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i I picked up gcc and binutils maintainership because the previous people who had been doing it sort of went silent. Maintaining these packages is not something that I want to do, however. Is anyone else interested in doing this? Maintaining binutils is relatively easy. I have one small patch that I keep in the distribution. It received some inexplicable resistance from binutils maintainers but I could probably push it in, if I had to. Maintaining gcc is harder due to the fact that you can't just build and release the FSF release. There are several additional patches required that, for some reason, the gcc maintainers don't seem to want to apply. There are also some patches that I've made to gcc to allow the -mno-cygwin option to work better. I doubt that they would be accepted in the mainline gcc. These currently are pretty 2.95.3 specific. Now that I've scared everyone off, is anyone interested in maintaining the cygwin gcc release? FWIW, I can still be of some help in my capacity as FSF gcc cygwin maintainer so I can get changes into the cygwin/mingw versions of gcc. If I don't hear from anyone here, I'm going to push this request to the cygwin mailing list, too. cgf