From: Arjan van de Ven <arjan@xxxxxxxxxxxxx> Date: Thu, 4 Oct 2007 10:50:46 -0700 > Ok every time something says anything not 100% positive about SLUB you > come back with "but it's fixed in the next patch set"... *every time*. I think this is partly Christoph subconsciously venting his frustration that he's never given a reproducable test case he can use to fix the problem. There comes a point where it is the reporter's responsibility to help the developer come up with a publishable test case the developer can use to work on fixing the problem and help ensure it stays fixed. Using an unpublishable benchmark, whose results even cannot be published, really stretches the limits of "reasonable" don't you think? This "SLUB isn't ready yet" bullshit is just a shamans dance which distracts attention away from the real problem, which is that a reproducable, publishable test case, is not being provided to the developer so he can work on fixing the problem. I can tell you this thing would be fixed overnight if a proper test case had been provided by now. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
