On Fri, Sep 14, 2012 at 9:12 AM, Troy Benjegerdes <[email protected]> wrote: >> > However, this requires having a much greater availability of release >> > management and testing resources. >> >> And perhaps an argument for automated tests that could prove out a release? >> If you mean manual testing resources, given the scope of platform support >> and myriad branches for OpenAFS I doubt 'enough' will ever be enough :) If >> we could bend those resources to creating and maintaining functional tests >> then that might be a better use of time. Definitely a challenge though. > > All this talk about 'reliable code for our users' is total BS > until 'make check' actually does some realisitic functionality tests. > > If you can't write an automated test for a feature, they I would > request we consider disabling that feature.
You have TFS forked. I suggest trying that approach and seeing what kind of filesystem you are left with. It will probably not involve kernel extensions. -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
