This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
So I think the real question here is, what warranted this kind of change in a "bug-fix" release? I think folks around here have gotten pretty unclear on the concept of maintenance releases, and everybody's playing fast and loose. This is just not the way to operate. That's why we have a development branch, for pete's sake. Are we going to have to add another level of ".x" to the versions to get a truly conservative maintenance release branch? And, Mark: I'm afraid the realities of packaging systems (and of humans) make it hopelessly unwise to attempt to have "the right thing" for anyone be to upgrade their shared libraries differently than they upgrade their development environment.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |