http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48426
--- Comment #16 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-11-07 19:49:39 UTC --- On Mon, Nov 07, 2011 at 07:25:32PM +0000, inform at tiker dot net wrote: > --- Comment #15 from Andreas Kloeckner <inform at tiker dot net> 2011-11-07 > 19:25:32 UTC --- > Zydrunas and I have successfully completed the copyright assignment process, > and we're ready to move forward with this patch. > Andreas, that's good news. If you are unaware of the submission policies, here's a short list: 1) Use 'svn diff > somefile.diff' to create the patch. The diff format should be unidiff (if possible). 2) Write ChangeLog entries. The ones you may need to worry about are gcc/fortran/ChangeLog, gcc/libgfortran/ChangeLog, and gcc/testsuite/gfortran.dg/ChangeLog. The ChangeLog entries should be separate from the diff. 3) Send the diff, ChangeLog entries, and a description of why and what you have done and how you tested the change to fortran@ and gcc-patc...@gcc.gnu.org.