Jean-Yves Migeon <[email protected]> wrote: > What about backwards compat then? ENOATTR != ENODATA, so any code that > used ENOATTR will now break. > > I remember reading that the attribute code was non-functional, and could > not be used. Are we sure that there is no other place where it could be > used but for another purpose?
You are right. We had no formal release with working extended attributes, therefore we cannot break backwardcompatibility. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz [email protected]
