From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30628 invoked by alias); 17 May 2005 17:19:46 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29733 invoked from network); 17 May 2005 17:18:44 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sourceware.org with SMTP; 17 May 2005 17:18:44 -0000 Received: (qmail 18316 invoked from network); 17 May 2005 17:18:42 -0000 Received: from localhost (HELO digraph.polyomino.org.uk) (joseph@127.0.0.1) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 17 May 2005 17:18:42 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.44) id 1DY5iK-0007nZ-M5; Tue, 17 May 2005 17:18:40 +0000 Date: Tue, 17 May 2005 17:56:00 -0000 From: "Joseph S. Myers" X-X-Sender: jsm28@digraph.polyomino.org.uk To: "Joel Sherrill " cc: Jonathan Wakely , Ralf Corsepius , GCC List Subject: Re: GCC 4.1: Buildable on GHz machines only? In-Reply-To: <428A1633.1030207@OARcorp.com> Message-ID: References: <17009.2368.986169.753001@cuddles.cambridge.redhat.com> <200505170311.03979.stevenb@suse.de> <20050517011655.GA25562@synopsys.com> <200505170331.25016.stevenb@suse.de> <1116321262.8237.837.camel@mccallum.corsepiu.local> <20050517093550.GA91912@compsoc.man.ac.uk> <428A1633.1030207@OARcorp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-05/txt/msg00907.txt.bz2 On Tue, 17 May 2005, Joel Sherrill wrote: > > For future reference, where patches should be sent is explained here: > > http://gcc.gnu.org/lists.html > > OK .. and Bugzilla or http://gcc.gnu.org/bugs.html references that link how? > > A search for "patch" in the bug reporting instructions does not mention > anything about cc'ing any patch list. The instructions on contributing to GCC, , do however link to lists.html for details of the appropriate lists, and give a lot of other information patch submitters will need to know. (This information about mailing lists used to be duplicated in contribute.html and lists.html, but that way it got out of sync.) I'm sure a patch to bugs.html to say "If you wish to submit a patch for a bug, see the instructions on contributing to GCC." would be considered. Likewise I suppose we could arrange for the Bugzilla pages for individual bugs to make prominent notices about how to contribute patches - the page for entering new bugs has a big notice "Before reporting a bug, please read the bug writing guidelines, please look at the list of most frequently reported bugs, and please search for the bug." so those for individual bugs could have a notice pointing patch contributors to contribute.html. -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ jsm@polyomino.org.uk (personal mail) joseph@codesourcery.com (CodeSourcery mail) jsm28@gcc.gnu.org (Bugzilla assignments and CCs)