On Tue, Jun 23, 2009 at 01:30:43PM -0600, lee wrote: > > I believe that the patch-2.6.29.x applies against the tree of 2.6.29, > > which is why some hunks would already be present if you try to apply > > it against 2.6.29.4. > > > > The easiest solution is to get the full 2.6.29.5 tree, or get the > > 2.6.29 tarball and then apply this patch. Someone correct me if I am > > wrong. > > My understanding is that patch-2.6.29.5 is supposed to patch (the full > source tree of) 2.6.29.4 to kernel version 2.6.29.5, the idea being > that it saves you from having to download the current full source > tree. Isn't that so? If I need to download the full source again, I'd > download 2.6.30 and won't need to patch anything. > > If you're right and some things that would be patched are already > present in their patched form, why isn't there an option to just skip > the parts that are already present and don't need to be patched?
Look at the "alternatives to patch" section here. Specifically, the interdiff part: http://www.mjmwired.net/kernel/Documentation/applying-patches.txt That should handle your problem. HTH. Kumar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org