Well, the task to make RPM apply as many patches as you want is almost trivial. I'm not quite sure about OpenSUSE spec files, but as to RedHat/Fedora ones you have to 1) enumerate the patches using Patch[0-99999] declarations, 2) apply patches in sequence using corresponding %patch[0-99999] directive in %prep section. Please notice it is completely up to you to maintain proper patch numbering and application sequence. I am not quite sure about maximal patch number that RPM accepts, but at least 5-digit values are usually fine. Adding tens lines of text to spec file is evidently less complicated task than merging hundreds lines of working kernel code. The last one is not also that complicated but is rather useless, dull and error-prone procedure. Once you correctly add those 20 lines to your spec file, you will be able to build the package as many times as you want with no risk to miss a part of the patch at all. In the hope it helps. -- Regards, Vladimir On Sat, 2015-02-21 at 16:59 +1100, doiggl@xxxxxxxxxxxxxxxxxx wrote: > Hello Ivan, > Can you provide a single patch for [1] when it accepted into Reiser4. > > [1] > [PATCHv5 00/10] reiser4: batch discard support (FITRIM ioctl): initial > implementation > > Reaon for asking: > Easier to apply one patch rather than ten and minimises risk of missing a > part of the patch. > > --Thanks Glenn > -- > To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
