Re: -mm -> 2.6.13 merge status

[Hans Reiser <reiser@namesys.com>]

Theodore Ts'o wrote:

>On Sat, Jun 25, 2005 at 12:23:41PM -0700, Hans Reiser wrote:
>  
>
>>>>       assert("trace_hash-89", is_hashed(foo) != 0);
>>>>
>>>>        
>>>>
>>Lots of people like corporate anonymity.  Some don't.  I don't.  I like
>>knowing who wrote what.  It helps me know who to pay how much.  It helps
>>me know who to forward the bug report to.   Losing your anonymity
>>exposes you, mostly for better since more communication is on balance a
>>good thing, but the fear is there for some.  I don't think we can agree
>>on this, it is an issue of the soul. 
>>    
>>
>
>Fallacy.
>
>The assert doesn't tell you who is at fault; it tells you who placed
>the assert which triggered; it could have triggered due to bugs caused
>by anyone, including the propietary binary-only module from Nvidia
>which the user loaded into his system....
>
>						- Ted
>
>
>  
>
If you read the thread again carefully, you will see that I already said
that it doesn't tell you who is at fault for the bug. Furthermore, I
said that the basis of the resistance of some developers to the use of
this is that they are not fully convinced that others understand that it
identifies only the assertion writer not the bug writer. As the boss of
the guys writing these assertions, I see no reason to indulge baseless
fears. When guys become experienced members of our team, they lose this
fear. Sending the bug report to the assertion writer often works nicely
as a first step, in my project, in my experience, in the cases where I
don't know anything about the likely implications of the assertion myself.