On Thu, Mar 03, 2005 at 06:03:36PM +0100, Jens Axboe wrote: > On Thu, Mar 03 2005, Chris Wright wrote: > > > - Finally: this tree never has any history past the "last release". When > > > a new kernel comes, the tree is frozen, and never to be touched again. > > > > I like this definition. The only remaining question is what determines > > a 2.6.x.y release? One patch? Sure if it's critical enough. > > Why should there be one? One of the things I like about this concept is > that it's just a moving tree. There could be daily snapshots like the > -bkX "releases" of Linus's tree, if there are changes from the day > before. It means (hopefully) that no one will "wait for x.y.z.2 because > that is really stable".
So that means we do the release often, _and_ provide -bkX snapshots daily if we happen to take a few days between releases and patches are pending for some reason. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
