2.11 branch status

Roland McGrath roland@hack.frob.com
Wed Aug 31 22:58:00 GMT 2011


> I did (on x86_64 and i586).  Besides the already reverted commit
> glibc-2.11.3-40-gc81fb72, I also had to revert commit
> glibc-2.11.3-33-g522cb50.  The thread starting at
> http://sourceware.org/ml/libc-alpha/2011-06/msg00006.html
> explains what was wrong with the original commit
> 4bff6e0175ed195871f4e01cc4c4c33274b8f6e3.

Ok.  Whatever the resolution it seems clear that was not a conservative and
safe change to backport.  I've reverted it too.

>From what I can see, 4bff6e01 remains on the trunk and hasn't been fixed
there or in the 2.14 branch.  Is that so?


Thanks,
Roland



More information about the Libc-alpha mailing list