backport 3.4 <- 3.5 after today's freeze, but prior to ssa merge?

[Paul Schlie]

I don't mean to imply that anything was wrong at the time, but given the
unforeseeable opportunity to have delayed it until just prior to the shortly
forthcoming ssa merge; simply observe that this may represent a potentially
beneficial opportunity to consider effectively doing so with hindsight.

-paul-

> From: Gabriel Dos Reis <gdr@integrable-solutions.net>
> Organization: Integrable Solutions
> Date: 15 Feb 2004 17:58:49 +0100
> To: Paul Schlie <schlie@comcast.net>
> Cc: <gcc@gcc.gnu.org>
> Subject: Re: backport 3.4 <- 3.5 after today's freeze, but prior to ssa merge?
> 
> Paul Schlie <schlie@comcast.net> writes:
> 
> | Sorry if it's a dumb notion, but as 3.5 appears to be as robust as 3.4
> | presently is; and be in effectively a similar temporary stage of development
> | pending it's merge with ssa; might it make sense to consider for the sake of
> | consistency and conservation of resources, focusing efforts on stabilizing
> | 3.5 for a few weeks, and then simply adopting it as the basis of 3.4 just
> | prior to it's merge with ssa, which afterward will then truly form the basis
> | of 3.5?
> 
> Is that different from having waited a few weeks before branching?
> I do not believe it is different.  But then, at the time the branch
> was created, that was for some reasons.  Going with your suggestion
> would mean that something is wrong with the branching at the time.  I
> cannot think of what.
> 
> -- Gaby