On Monday 12 May 2014 at 20:52:27, doiggl@xxxxxxxxxxxxxxxxxx wrote: > Hello, > How do you apply these patches [1] to kernel source code ?. > So far I have applied this patch [2] to the kernel source code. > > Do I save each as a txt .patch file and apply with command > # patch < patch.file > > I using linux-3.14.tar.xz > --Thanks Glenn > > > [1] > [PATCHv3 1/5] reiser4: discard support: make space_allocator's > check_blocks() > . > . > [PATCHv3 5/5] reiser4: discard support: downgrade all reiser4_log() to > reiser4_debug(). > > http://www.spinics.net/lists/reiserfs-devel/msg03886.html > > [2] > reiser4-for-3.14.1.patch > > -- > 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 These git-formatted patches (1) are saved to text files "as is" (as in mailbox) and then applied using `patch -p1 -i $patch` or `patch -p1 < $patch` on top of a source tree with reiser4 (2) itself already applied. Actually, if you have a git tree, you can also do `cat $all_patches | git am` on top of that tree. This will keep commit metadata, applying each patch as a separate commit. Thanks, -- Ivan Shapovalov / intelfx /
Attachment:
signature.asc
Description: This is a digitally signed message part.
