>> Apart from the notification, surely this can be done at the
>> back-end level with file permissions (ideally ACLs even 8) ?
> Generally, filesystem perms, even ACLs, aren't quite enough to deal
> with the kind of permissions you'd want in a repository, and given
> the discussions of proceedure here, the kernel is going to need
> some pretty detailed perms work if it goes into CVS.
===8<=== CUT ===>8===
What I would personally like to see is a system whereby people
submitting reports stated what kernel options they'd used, and some
sort of auto-analyser could then check to see what options weren't
appearing in reports on the basis that untested options are more
likely to contain bugs than heavily tested ones...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/