From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thomas Koenig Newsgroups: gmane.comp.gcc.fortran,gmane.emacs.devel Subject: Re: Emacs and GFortran Date: Thu, 2 Nov 2006 20:00:05 +0100 Message-ID: <20061102190005.GA6116@meiner.onlinehome.de> References: <200611011037.12356.wt@atmos.colostate.edu> <20061101180354.GA62686@troutmask.apl.washington.edu> <20061101203931.E775C4401A@Psilocybe.Update.UU.SE> <20061101213056.GA63890@troutmask.apl.washington.edu> <20061101215142.51A0944013@Psilocybe.Update.UU.SE> <20061101223548.GA72295@troutmask.apl.washington.edu> <20061101224912.ED10144013@Psilocybe.Update.UU.SE> <20061101232634.GA44475@troutmask.apl.washington.edu> <20061102132624.0D3E74400B@Psilocybe.Update.UU.SE> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1162494169 2076 80.91.229.2 (2 Nov 2006 19:02:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 2 Nov 2006 19:02:49 +0000 (UTC) Cc: Steve Kargl , wt@atmos.colostate.edu, fortran@gcc.gnu.org, emacs-devel@gnu.org Original-X-From: fortran-return-15416-gcgf-fortran=m.gmane.org@gcc.gnu.org Thu Nov 02 20:02:44 2006 Return-path: Envelope-to: gcgf-fortran@gmane.org Original-Received: from sourceware.org ([209.132.176.174]) by ciao.gmane.org with smtp (Exim 4.43) id 1GfhnY-0007KB-2b for gcgf-fortran@gmane.org; Thu, 02 Nov 2006 20:00:22 +0100 Original-Received: (qmail 26512 invoked by alias); 2 Nov 2006 19:00:18 -0000 Original-Received: (qmail 26494 invoked by uid 22791); 2 Nov 2006 19:00:16 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,FORGED_RCVD_HELO,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Original-Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.183) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 02 Nov 2006 19:00:01 +0000 Original-Received: from [80.134.50.243] (helo=meiner.onlinehome.de) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1Gfhn83juR-0007T6; Thu, 02 Nov 2006 19:59:56 +0100 Original-Received: from ig25 by meiner.onlinehome.de with local (Exim 3.36 #1 (Debian)) id 1GfhnJ-0001gc-00; Thu, 02 Nov 2006 20:00:05 +0100 Original-To: "Alfred M. Szmidt" Content-Disposition: inline In-Reply-To: <20061102132624.0D3E74400B@Psilocybe.Update.UU.SE> User-Agent: Mutt/1.5.13 (2006-08-11) X-Provags-ID: kundenserver.de abuse@kundenserver.de login:82006718d44785d1b0aefbb6e084916e X-IsSubscribed: yes Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Post: List-Help: , Original-Sender: fortran-owner@gcc.gnu.org Xref: news.gmane.org gmane.comp.gcc.fortran:15385 gmane.emacs.devel:61619 Archived-At: On Thu, Nov 02, 2006 at 02:26:24PM +0100, Alfred M. Szmidt wrote: (addressed to Steve Kargl) > Or better yet, this will take > even less time than posting this data: simply fix the bug! You are proposing a patch to gfortran, which is part of gcc. The guidelines for accepting contributions are spelled out on the gcc website. If your patch is non-trivial, we need copyright papers from you assigning copyright of any changes to the gcc source tree to the FSF. Do you have a copyright assignment? In order to be included into gcc, your proposed patch needs to be regression-tested and accompanied by relevant test cases proper ChangeLog entries. If these conditions are met, then post the patch to gcc-patches@gcc.gnu.org and fortran@gcc.gnu.org. Usually there will be a discussion of the patch, possibly leading to requirements for changes. Finally, if all goes well, a maintainer will approve the patch and (if you don't have commit privileges) commit it. That's the way gcc and gfortran maintenance works. In practice, it works pretty well. Best regards Thomas