Found 9 matching messages (0.040 seconds). Page 1 of 1.
Michael Kerrisk wrote:
> On 4/15/08, David Newall
linux-netdev - David Newall - Apr 15 2008 - 10:04
Ingo Molnar wrote:
> * David Newall
linux-netdev - David Newall - Jul 22 2008 - 10:54
david@lang.hm wrote: > I'd rather have a developer/maintainer who introduces and fixed 100 > bug, but fixes them promptly, And I'd rather be able to see that that person introduced 100 bugs than to have no idea. As has been said before, the current ...
linux-netdev - David Newall - Apr 16 2008 - 05:06
James Morris wrote: > I don't know how to solve this, but suspect that encouraging the use of > reviewed-by and also including it in things like analysis of who is > contributing, selection for kernel summit invitations etc. would be a > start. At
linux-netdev - David Newall - Apr 15 2008 - 05:33
Rafael J. Wysocki wrote: > Well, even if someone introduces bugs relatively frequently, but then also > works with the reporters and fixes the bugs timely, it's about okay IMO. > This really is not okay. Even if bugs are fixed a version or two
linux-netdev - David Newall - Apr 15 2008 - 22:34
Jesper Juhl wrote: > Interresting. Just be careful results are produced for the big picture > and not used to point fingers at individuals. > If there are individuals at whom a finger needs to be pointed, this system will highlight them, and
linux-netdev - David Newall - Apr 17 2008 - 13:04
These patches, which simply play around with white space, are undesirable, in my opinion. It doesn't make the code better, just changes the aesthetics to one that's more to your liking, and surely it makes it less pleasing to others. I see no benefit
linux-netdev - David Newall - Jun 15 2008 - 02:21
Németh Márton wrote: > # define DPRINTK(fmt, args...) \ > - printk(KERN_DEBUG "%s: " fmt, __FUNCTION__ , ## args) > + printk(KERN_DEBUG "%s: " fmt, __func__ , ## args) > Why change __FUNCTION__ to __func__? I don't even know where __func__
linux-netdev - David Newall - Jun 15 2008 - 02:26
Ingo Molnar wrote: > hm, the distcc TCP hangs are back: > The missing four client-side connections are more interesting than the unsent data. > I.e. the client side send-queue is stuck in established state, server > side thinks it's a proper
linux-netdev - David Newall - Jul 22 2008 - 09:45