From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22997 invoked by alias); 9 Apr 2011 07:30:51 -0000 Received: (qmail 22970 invoked by uid 22791); 9 Apr 2011 07:30:47 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_SV X-Spam-Check-By: sourceware.org Received: from mailout-de.gmx.net (HELO mailout-de.gmx.net) (213.165.64.22) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sat, 09 Apr 2011 07:30:41 +0000 Received: (qmail invoked by alias); 09 Apr 2011 07:30:40 -0000 Received: from xdsl-89-0-74-23.netcologne.de (EHLO localhost.localdomain) [89.0.74.23] by mail.gmx.net (mp016) with SMTP; 09 Apr 2011 09:30:40 +0200 Received: from ralf by localhost.localdomain with local (Exim 4.72) (envelope-from ) id 1Q8Sct-0008Pv-EC; Sat, 09 Apr 2011 09:30:35 +0200 Date: Sat, 09 Apr 2011 07:30:00 -0000 From: Ralf Wildenhues To: Georg-Johann Lay Cc: Gerald Pfeifer , "Weddington, Eric" , gcc-patches@gcc.gnu.org, Anatoly Sokolov , Denis Chertykov Subject: Re: [Ping #2][Patch, testsuite]: Don't xfail sibcalls on AVR Message-ID: <20110409073035.GA31779@gmx.de> Mail-Followup-To: Ralf Wildenhues , Georg-Johann Lay , Gerald Pfeifer , "Weddington, Eric" , gcc-patches@gcc.gnu.org, Anatoly Sokolov , Denis Chertykov References: <4D919FAC.1090406@gjlay.de> <4D9ADB77.1010500@gjlay.de> <8D64F155F1C88743BFDC71288E8E2DA80134B2E4@csomb01.corp.atmel.com> <4D9C466D.90507@gjlay.de> <8D64F155F1C88743BFDC71288E8E2DA80134B3C4@csomb01.corp.atmel.com> <4D9C62A4.1060908@gjlay.de> <4D9ED5B5.4030208@gjlay.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D9ED5B5.4030208@gjlay.de> User-Agent: Mutt/1.5.20 (2010-08-04) X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg00675.txt.bz2 * Georg-Johann Lay wrote on Fri, Apr 08, 2011 at 11:30:29AM CEST: > Gerald Pfeifer schrieb: > > Nope. All you need is a maintainer (Eric, Denis and Anatoly all > > qualifying) to sponsor your request. Obviously that mostly makes > > sense if you expect to contribute more than a handfull of patches > > over the course of the next year, which we do hope will be the > > case. :-) > Thanks for that hint. Is that the "Write after Approval" section in > MAINTAINERS? Yes. > However, I have bunch of questions for that I don't find answers in > the wiki. As it is very easy *not* to find something in the gcc wiki, > I probably just missed it... > > 1) What is the exact procedure for this? Will it be like fsf copyright > assignment and take more than a year (at least in my case) to pass? Somebody says "you can mention me as sponsor", you put him or her in the approval in the form you fill out after reading http://gcc.gnu.org/svnwrite.html and wait for the login to be approved. In my case, it took 3 hours, but I wouldn't worry if it took a weekend plus a couple of workdays until one of the sourceware people has time. > 2) Changelogs and svn logs are always in sync. Is there some setup > in the svn server to do this magic? Are there custom scripts for > this or is it all hand-made? FWIW, some people use a script named mklog[1], a while ago I wrote vc-chlog[2] for generating stub ChangeLog entries. I generate the svn log entries from the ChangeLog entries with a couple of editor macros, dunno if there's public scripting for that. > 3) Ditto for PRs that get a notification as soon as a patch goes > upstream. The mechanism is triggered by the PR category/12345 entries in the log. The category is the 'Component' field in bugzilla. > 4) Will there be someone like a mentor who I could ask such > questions or get useful hints? I'm not aware of a special mentor program for new contributors, but people here assume that beginners make beginner errors, read and search mailing lists and/or the wiki and web pages, and learn. I wouldn't worry too much, you'll be corrected. ;-) Cheers, Ralf [1] http://sourceware.org/gdb/wiki/DeveloperTips [2] http://www.gnu.org/software/vc-dwim/