On Tue, 23 Jun 2009 12:11:52 -0700 (PDT) Linus Torvalds wrote:Makes sense. It certainly is counter-intuitive sometimes, though. Just to clarify, there would seem to be one other category of bugs that is reasonable post-merge-window: those introduced by new features (or bug fixes) that were added during the merge window (i.e. something found in testing the new code during the -rc cycle). Those don't necessarily have to be security/oops problems and, for the most part, can't be regressions (at least for new features). Or should those wait, by and large, for the next merge window? jake -- Jake Edge - LWN - jake@lwn.net - http://lwn.net -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Linus Torvalds | Re: LSM conversion to static interface |
| Ingo Molnar | [patch 03/13] syslets: generic kernel bits |
| Ingo Molnar | Re: [PATCH 6/6] sched: disabled rt-bandwidth by default |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| David Miller | [GIT]: Networking |
| Gregory Haskins | [RFC PATCH 00/17] virtual-bus |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
