On Thu, Feb 13, 2003 at 03:16:29PM -0600, Paul Larson wrote:
> Ideally, there should be no waiting around for replies. The message is
> sent, he starts whatever build/boot test cycle, checks for replies when
> he's done and ready to release. If nothing looks urgent enough to hold
> it up, then he pushes the release. I still don't see how this adds any
> kind of terrible delay.
Outside suggestions to "improve" Linus's workflow usually fall upon deaf
ears...
IMO to accomplish your goals, set up a test box with BitKeeper,
constantly pulling and testing the latest 2.5.x BK trees. If they
crash, send full info to lkml.
Enough crash messages, and people will know automatically whether or not
the kernel is good... and Linus didn't have to be bothered at all.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:49 EST