On Wed, 30 Apr 2008, David Miller wrote:I'm not saying we should merge crap. You can take any argument too far, and clearly it doesn't mean that we should just accept *anything*, because it will magically be gilded by its mere inclusion into the kernel. No, I'm not going to argue that. But I do want to argue against the notion that the only way to raise quality is to do it before it gets merged. It's often better to merge early, and fix the issues the merge brings up early too! Release early, release often. That was the watch-word early in Linux kernel development, and there was a reason for it. And it _worked_. Did it mean "release crap, release anything"? No. But it did mean that things got lots more exposure - even if those "things" were sometimes bugs. Linus --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Ingo Molnar | Re: [RFT] x86 acpi: normalize segment descriptor register on resume |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Ingo Molnar | [bug] stuck localhost TCP connections, v2.6.26-rc3+ |
