Josef Karthauser wrote:
> The reason for adopting a fall back solution it that it is not clear that
> setflags/getflags is the best choice of function name for manipulating
> file flags as it's a bit too generic a name. Whilst we're debating
> this point there's no point in having them as library calls for
> 4.0.
Agreed. When {g|s}etflags is in libc for 4.0-RELEASE, we can't remove
(or rename) them later without bumping libc's version number, because
it basicly is an (backward) incompatible interface change. If there's
a remote change that the functions are to be removed or renamed, we
should make sure it's done before -RELEASE.
The patch looks good, but contains style (ordering) bugs :-)
I can't actually test the patch, but assume that's been done.
marcel
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
