>> >>> But I'd like to see a coherent >>> explanation of how the functionality offered by DEPT is clearly better. >> >> Yes, that's also what I am missing. >> >> Stating that lockdep is stable and should not be destabilized is not really a >> good argument. > > No it is not. We change "stable" things all the time. Replacing one > big thing with another big thing is almost always rejected. > Incremental development is the preferred approach. > So developing something like DEPT to explore and learn and demonstrate > a cool idea is great. Making it completely separate can give a > developer freedom to innovate. > But the path from there to upstream acceptance is to take the lessons > learned and to apply them one by one to the existing tools. > Yes, that takes longer. Yes it can be frustrating. Yes you need to > be able to work with people - not just code - to bring the community > along with you. > But the result is generally much better. I mean, I agree, and that's likely the direction DEPT should take.
... unless there is something so fundamental different that it cannot possibly be integrated into lockdep ... or can but overcomplicates things such that it really must stay separate. -- Cheers, David
