On Wed, Mar 09, 2005 at 03:57:16PM -0800, Matt Mackall wrote: > Imagine we want to go from 2.6.11.3 to 2.6.12
The easiest way would be to keep a local fresh copy of 2.6.11 before applying 2.6.11.3 anyway. That would solve a) and b) even more easily. And yes, I find a) more logical. This is the way all private trees have been working for ages. When you download 2.6.11-ac2, it's not a patch against -ac1, but against 2.6.11. If you want to start from -ac1, you get the 2.6.11-ac1-ac2 patch. And last, since these patches are mostly bugfixes for the reference kernel (eg: 2.6.11), it seems logical to be able to patch that kernel with the latest bug fix. cheers, willy > case a) > revert patch 2.6.11.3 > get and apply 2.6.12 > > case b) > revert patch 2.6.11.3 > revert patch 2.6.11.2 > revert patch 2.6.11.1 > get and apply 2.6.12 > > case c) > poke around on kernel.org and figure out that the last kernel in .11 is .11.5 > get and apply 2.6.11.4 > get and apply 2.6.11.5 > get and apply 2.6.12 > > Note this gets increasingly more painful in cases b and c when there > are a large number of post-releases. And case c) is really stupid when > you want to go from 2.6.12 to 2.6.11. > > Also note that -pre, -rc, -bk, -mm, -ac, and every other branch off a > release has worked the a) way. > > -- > Mathematics is the supreme nostalgia of our time. > - > 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/ - 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/
