This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Roland McGrath wrote: > I favor #3, backing out the new syscalls and holding off on all ABI > additions on the trunk for another month or two while we get a > stabilization release or two out. Hell, no. We are using the trunk in rawhide and the same is likely true for others. It serves a good purpose: enable new functionality to be tested. Be it in the kernel or in libc itself. And of course there won't be a GLIBC_2.4.1 version. If you don't want to maintain a branch yet this is fine. With the limitations of CVS this can probably be easiest achieved by cutting for the time being for every dot-dot release a new branch and on the branch back out the few changes (Makefile & headers) which are visible. That's a few minutes worth of work. -- â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |