I'm looking at the upstream CVS, and I notice that the following has happened since our last snapshot in September: 1) Timezone updates 2) Major regex redo to support utf-8 at decent speeds. 3) A pile of hppa fixes, removing much ugly hackery. 4) hurd works again 5) execstack fixes 6) ia64 debugging fixes 7) major nptl speed fix. 8) locale fixes 9) s390 debugging fixes At the same time, I don't see any major changes that break the workarounds we have (to provide errno, hw optimisations) nor any major new features (like the thread cancellation interface and such). We were holding off a new cvs update until the Sarge release. That doesn't appear to be soon, since there are still buildds that are offline. Also, given drepper's reluctance to ever release a new version, and prediction of no major changes in the near future[0], it seems that doing a cvs update might not only be worth doing, but also be relatively safe. Also, we have 88 dpatch files right now. It's a bit daunting. Assuming consensus, I would prepare this as 2.3.3-1 [1] for experimental for ia64, sparc and alpha, and do it for i386 as soon as it can be built again. We now have excessively good bandwidth at work, so if there's tests people want run like "Build the archive", I can do those now. Tks, Jeff Bailey [0] http://sources.redhat.com/ml/libc-hacker/2003-11/msg00150.html [1] http://sources.redhat.com/ml/glibc-cvs/2003-q4/msg00518.html -- In the United States, there isn't a government database that hasn't been misused by the very people entrusted with keeping its information safe. - Bruce Schneier
Attachment:
signature.asc
Description: This is a digitally signed message part