Hi stable release managers, For a few upstream releases now, some people are maintaining a stable branch for some versions of the glibc [1], which is followed by eglibc [2]. This is the case for the 2.11 version we are using in Squeeze, it is not sure yet which next version will have a long term support. The branch only consists of patches cherry-picked from HEAD after a few weeks. Some of the patches in this branch fix already reported bugs [3], but some of them [4] are likely to be reported later during Squeeze lifetime.
I am therefore thinking about uploading the next upstream stable version (2.11.4 is currently in test period, it will be released in the next days), similarly to what is currently done for the kernel. What's your opinion on that, is it something that you would allow? Thanks, Aurelien [1] http://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.11/master [2] http://www.eglibc.org/cgi-bin/viewcvs.cgi/branches/eglibc-2_11/ [3] http://sourceware.org/git/?p=glibc.git;a=commit;h=2796cd94a85e1d6a5acb2a86e2c6cc41abc33efa [4] http://sourceware.org/git/?p=glibc.git;a=commit;h=78856c5c73f74d2a850da0a62393dca9dd5a2df4 -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110605102351.ga3...@hall.aurel32.net
