This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Fortran] Massive whitespace patch.
On Mon, Jan 01, 2007 at 03:31:14PM -0800, Brooks Moses wrote:
> Steve Kargl wrote:
> >On Mon, Jan 01, 2007 at 11:34:33PM +0100, Thomas Koenig wrote:
> >> What will this do to backports to 4.2?
> >
> >I'm not sure what you mean. This change does not
> >prevent anyone from back porting something in trunk
> >to 4.2. In fact, gfortran should be following the
> >standard GCC guidelines with regard to back porting
> >to 4.2 (i.e, regression fixes only).
>
> I think what Thomas is referring to is that any patchfile for 4.3 that
> touches a spot with changed whitespace will not apply to 4.2, and will
> thus require hand editing of the files to backport. This makes
> backporting things substantially more laborious than the "apply the
> patch and regtest" process that it is now.
I'm well aware of this complication. But, I stand by my assertation
that the whitespace patch does not prevent back porting. See
http://en.wikipedia.org/wiki/Backport
> (My personal opinion is that this annoyance and extra work does not
> outweigh the value of doing a style cleanup. I'm not sure about timing,
> though -- I can see arguments for why it might be useful to hold off
> until the 4.2 release, but I don't have any opinion one way or the other
> on their validity.)
The timing is such that I will not work on the ISO C Binding
branch until after the whitespace patch is merged into branch.
This is perhaps the last major feature I will work on fixing.
--
Steve