> I forgot to mention on rather important factor in this equation: Er, this is the *only* important factor. IMHO, it made most of the previous conversation be completely off-the-rails.
> If nothing happens, vinum is going to break even more very soon. No ... if you do a commit that changes the code assumptions upon which vinum was built, vinum will break. vinum is not going to "magically" break by itself. This gets back to a problem with the FreeBSD development model: people who commit changes that break things in other parts of the system do not automatically get assigned the responsibility to fix them. Now, there's no way to impose something like that requirement on a cooperative anarchy, so I am not playing the "let's reorganize" card -- I think most of us would agree that "that dog won't hunt" as we say down around these parts. But, in the real world of software engineering, He Who Breaketh It, Must Fixeth It. Your mileage may vary. mcl _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
