Re: [RFA] import drow dbxread.c fix to branch

[Andrew Cagney <ac131313@cygnus.com>]

>> > If we still have problems for which such solutions are 
>> > impossible, but which are deemed too grave to not solve them in 5.2, it 
>> > would mean that the branch was cut too early, and we should consider 
>> > canceling the branch and starting the release cycle anew.

I've known about this one for a month or so - ever since JimB approved 
FredF's symtab change and MichaelC promptly flaged the regressions it 
caused.

As far as I know, my options were:

- delay the branch until it the regressions were fixed (an unknown time 
frame)

- branch but threaten to pull the patch unless JimB (who approved it) 
fixed the problem

- branch and ship with the regression (not an option)

I went with the second option.

Fortunatly (for JimB), DanielJ found a fix for the problem and that has 
slowly been working its way into the branch.

>> That's always an option.  My opinion at this time is that we are not
>> at all close to needing a re-branch.
> 
> 
> I wrote that because the number of changes that are retrofitted into the 
> branch is disturbingly high (IMHO).  Perhaps Andrew should have held us 
> under the threat of the branch slightly longer.
> 
> I alwaus thought that a branch is effectively feature-frozen.  Perhaps I 
> misunderstood the policy.

This one is a regression :-(

Andrew