Lines Matching +full:right +full:- +full:most
11 This document is obsolete. In most cases, rather than using ``patch``
54 in the patch file when applying it (the ``-p1`` argument to ``patch`` does
57 To revert a previously applied patch, use the -R argument to patch.
60 patch -p1 < ../patch-x.y.z
64 patch -R -p1 < ../patch-x.y.z
76 patch -p1 < path/to/patch-x.y.z
82 Patch can also get the name of the file to use via the -i argument, like
85 patch -p1 -i path/to/patch-x.y.z
91 xzcat path/to/patch-x.y.z.xz | patch -p1
92 bzcat path/to/patch-x.y.z.gz | patch -p1
96 gunzip or xz on the file -- like this::
98 gunzip patch-x.y.z.gz
99 xz -d patch-x.y.z.xz
101 Which will leave you with a plain text patch-x.y.z file that you can feed to
102 patch via stdin or the ``-i`` argument, as you prefer.
104 A few other nice arguments for patch are ``-s`` which causes patch to be silent
106 screen too fast, and ``--dry-run`` which causes patch to just print a listing of
107 what would happen, but doesn't actually make any changes. Finally ``--verbose``
121 If patch encounters something that doesn't look quite right it has two
125 One example of something that's not 'quite right' that patch will attempt to
136 right it doesn't /always/ get it right, and the result will sometimes be
144 If you don't have any third-party patches applied to your kernel source, but
150 re-downloading the patch and if things are still not OK then you'd be advised
156 find a file to be patched. Most likely you forgot to specify -p1 or you are
158 applied with ``-p0`` instead of ``-p1`` (reading the patch file should reveal if
159 this is the case -- if so, then this is an error by the person who created
179 If you get ``Reversed (or previously applied) patch detected! Assume -R? [n]``
183 If you actually did apply this patch previously and you just re-applied it
185 previously and actually intended to revert it, but forgot to specify -R,
220 step. The -z flag to interdiff will even let you feed it patches in gzip or
226 interdiff -z ../patch-4.7.2.gz ../patch-4.7.3.gz | patch -p1
245 Most recent patches are linked from the front page, but they also have
248 The 4.x.y (-stable) and 4.x patches live at
252 The -rc patches live at
261 release is the most recent.
263 If regressions or other serious flaws are found, then a -stable fix patch
270 base 4.x kernel -- if you need to move from 4.x.y to 4.x+1 you need to
277 $ cd ~/linux-4.6 # change to kernel source dir
278 $ patch -p1 < ../patch-4.7 # apply the 4.7 patch
280 $ mv linux-4.6 linux-4.7 # rename source dir
284 $ cd ~/linux-4.6.1 # change to kernel source dir
285 $ patch -p1 -R < ../patch-4.6.1 # revert the 4.6.1 patch
287 $ patch -p1 < ../patch-4.7 # apply new 4.7 patch
289 $ mv linux-4.6.1 linux-4.7 # rename source dir
295 Kernels with 3-digit versions are -stable kernels. They contain small(ish)
299 This is the recommended branch for users who want the most recent stable
308 The -stable team usually do make incremental patches available as well
310 non-incremental ones below. The incremental ones can be found at
323 $ cd ~/linux-4.7.2 # change to the kernel source dir
324 $ patch -p1 -R < ../patch-4.7.2 # revert the 4.7.2 patch
325 $ patch -p1 < ../patch-4.7.3 # apply the new 4.7.3 patch
327 $ mv linux-4.7.2 linux-4.7.3 # rename the kernel source dir
329 The -rc kernels
332 These are release-candidate kernels. These are development kernels released
337 you intend to run them. This is however the most stable of the main
344 stuff (such people should see the sections about -next and -mm kernels below).
346 The -rc patches are not incremental, they apply to a base 4.x kernel, just
347 like the 4.x.y patches described above. The kernel version before the -rcN
348 suffix denotes the version of the kernel that this -rc kernel will eventually
351 So, 4.8-rc5 means that this is the fifth release candidate for the 4.8
356 # first an example of moving from 4.7 to 4.8-rc3
358 $ cd ~/linux-4.7 # change to the 4.7 source dir
359 $ patch -p1 < ../patch-4.8-rc3 # apply the 4.8-rc3 patch
361 $ mv linux-4.7 linux-4.8-rc3 # rename the source dir
363 # now let's move from 4.8-rc3 to 4.8-rc5
365 $ cd ~/linux-4.8-rc3 # change to the 4.8-rc3 dir
366 $ patch -p1 -R < ../patch-4.8-rc3 # revert the 4.8-rc3 patch
367 $ patch -p1 < ../patch-4.8-rc5 # apply the new 4.8-rc5 patch
369 $ mv linux-4.8-rc3 linux-4.8-rc5 # rename the source dir
371 # finally let's try and move from 4.7.3 to 4.8-rc5
373 $ cd ~/linux-4.7.3 # change to the kernel source dir
374 $ patch -p1 -R < ../patch-4.7.3 # revert the 4.7.3 patch
375 $ patch -p1 < ../patch-4.8-rc5 # apply new 4.8-rc5 patch
377 $ mv linux-4.7.3 linux-4.8-rc5 # rename the kernel source dir
380 The -mm patches and the linux-next tree
383 The -mm patches are experimental patches released by Andrew Morton.
385 In the past, -mm tree were used to also test subsystem patches, but this
387 `linux-next <https://www.kernel.org/doc/man-pages/linux-next.html>`
388 tree. The Subsystem maintainers push their patches first to linux-next,
391 The -mm patches serve as a sort of proving ground for new features and other
393 Once such patches has proved its worth in -mm for a while Andrew pushes
396 The linux-next tree is daily updated, and includes the -mm patches.
398 lot of debugging patches not appropriate for mainline etc., and is the most
403 sure you have up-to-date backups -- that goes for any experimental kernel but
404 even more so for -mm patches or using a Kernel from the linux-next tree).
406 Testing of -mm patches and linux-next is greatly appreciated since the whole
411 But testers of -mm and linux-next should be aware that breakages are