![]() | |||||||||||||
Messages in this thread |
Bill Davidsen wrote: > Matt Mackall wrote: > >> In your world, do you want to do: >> >> cp -rl linux-2.6.11 linux-2.6.11.5 >> cd linux-2.6.11.5 >> bzcat ../Patches/patch-2.6.11.1.bz2 | patch -p1 >> bzcat ../Patches/patch-2.6.11.2.bz2 | patch -p1 >> bzcat ../Patches/patch-2.6.11.3.bz2 | patch -p1 >> bzcat ../Patches/patch-2.6.11.4.bz2 | patch -p1 >> bzcat ../Patches/patch-2.6.11.5.bz2 | patch -p1 >> >> I suspect you might find that tedious, especially if only the last one >> addressed a bug that affected you. > > > Being lazy, I would do > bzcat ../Patches/patch-2.6.11.*.bz | patch -p1 > (or similar). But as I posted long ago when this discussion started it > is desirable to have both. > being super lazy I'd type: scripts/patch-kernel . ../Patches nb it's currently broke as mentioned in another thread: Re: [BUG] Re: [PATCH] scripts/patch-kernel: use EXTRAVERSION being fixed though. It will (I assume!) embody whatever rules are needed to revoke patches to go from 2.6.11.5 to 2.6.12 (and since I think the new version has d/l facilities, that should assist in the case of a base kernel d/l of 2.6.11.3 for which no local patches exist to revert prior to patching to 2.6.12) David - 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/ | ||||||||||||
| Last update: 2005-03-22 14:11 [from the cache] ©2003-2008 | |||||||||||||