On Mon, 2008-04-14 at 03:22 -0700, Andrew Morton wrote:I'm not sure I agree. There is a habit of treating people who post crap code as somehow inferior to the purer old-timers, certainly. And that's probably not such a good thing, but at least it helps to keep the signal:noise ratio down a little, overall. But except to the extent that there is a correlation between 'corporate developers' and 'people who post crap code', I wouldn't agree with your statement above. We have a lot of people working for large corporations who don't post crap code, and to whom Christoph almost never promotes an attitude of violence. Looking at Jon's 'who wrote 2.6.23' analysis, I see quite a lot of successful 'corporate' involvement. Anyone trying to defend crap code _should_ be limited in their options, surely? And sometimes, 'corporate developers' do try to defend crap code, because they've made traditional corporate mistakes like developing it all in private and presenting it as a fait accomplis without proper a priori review, and/or haven't budgeted for the necessary time to fix it. -- dwmw2 --
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Joerg Roedel | [PATCH 03/34] AMD IOMMU: add defines and structures for ACPI scanning code |
| Eric W. Biederman | [PATCH] powerpc pseries eeh: Convert to kthread API |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
