This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Backporting, was: Re: [PATCH, libgfortran] PR24794 namelist input of character array]


On Tue, Nov 22, 2005 at 07:04:34PM +0100, Tobias.Schlueter@Physik.Uni-Muenchen.DE wrote:
> Quoting Steve Kargl <sgk@troutmask.apl.washington.edu>:
> > On Tue, Nov 22, 2005 at 06:51:43PM +0100, Paul Thomas wrote:
>>> Jerry,
>>>>
>>>>OK for Trunk?  OK for 4.0-branch?
>>>>
>>> I have reviewed and regtested the thread-safe version.  It looks good to
>> me.
>>>
>>> OK for trunk, OK for 4.1 and...., well what are we doing here?
>>>
>>
>> For my patches and commits, if a patch applies cleanly to 4.0,
>> then I'll update the 4.0 source tree; otherwise, I'll leave
>> 4.0 alone.
> 
> We should definitely stop merging changes to 4.0, unless they are
> regressions from g77, and even this will be of debatable value after
> the release of 4.1. 

IMHO, 4.0 should be left alone after 4.1 is released.  We, the gfortran
developers, simply don't have enough man power for 2 branches and
mainline.

> I'm not so sure that we're in a state where our policy of backporting
> all fixes to 4.1 costs us more than it gains us, so we might want to
> continue this.
> 
> Opinions?

Mainline and 4.1 are in sync.  I think we should try to maintain
this for as long as possible.  The biggest change coming in mainline
with major implications for gfortran is openmp.  When the openmp
infrastructure is meged into mainline, I think that is where we will
again diverge unless rth, Diego, and Jakub backport all of openmp to
4.1.

-- 
Steve


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]