Re: glibc 2.1.3pre1 with Linuxthreads 2.1.3pre2 made my applicationworkagain

[Kai Engert <engert at isg dot de>]

Kaz Kylheku wrote:
> 
> On Sun, 30 Jan 2000, Kai Engert wrote:
> 
> > Ok, so people not using this mechanism shouldn't be required to update
> > :-)
> 
> That is actually reasonable, so no smiley required. If your application is not
> affected by an issue and its fix, I wouldn't recommend that you upgrade (for
> the sake of getting just that fix.) The fixes are not without risk, and the
> fixed library is only a pre-release version that hasn't been tested by a lot of
> people. There are also other changes in it, like design changes to the
> read-write lock code to make writer preference work while obeying Unix98.

Ok.

> > Do you think, as soon as glibc 2.1.3 is released, someone should make an
> > announcement to comp.programming.threads, mentioning the fix and
> > recommending to update?
> 
> I think it has already been debated enough in comp.programming.threads, but it
> could be worthwhile nevertheless. Or perhaps the newsgroups
> comp.os.linux.announce or c.o.l.development.{system,apps}.  Anyone doing
> serious Linux development should keep up with mailing lists like libc-alpha,
> and the kernel mailing lists, and watch the newsgroups. Developers who don't
> pay attention to what is going on in the community are on their own.

I must admit, I didn't follow those newsgroups.
It's hard to be up to date with everything that could be relevant.

But thanks for the hints which groups are important to read, 
I wil pay more attention to them in the future.

Best regards,
Kai