summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2016-10-26 16:48:36 -0600
committerJonathan Corbet <corbet@lwn.net>2016-10-27 16:38:29 -0600
commit67972a539e9ff1a3ed794c463c4e544442df693e (patch)
tree61bc1bd043846d37880f826f5952c8f2781dafef
parent31b24bee33572031632c33091bb73ed0e949c53a (diff)
downloadlinux-stable-67972a539e9ff1a3ed794c463c4e544442df693e.tar.gz
linux-stable-67972a539e9ff1a3ed794c463c4e544442df693e.tar.bz2
linux-stable-67972a539e9ff1a3ed794c463c4e544442df693e.zip
docs: Add a warning to applying-patches.rst
This is ancient stuff and we don't do things this way anymore. In the absence of simply deleting the document, at least add a warning to it. Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/process/applying-patches.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/process/applying-patches.rst b/Documentation/process/applying-patches.rst
index abd7dc7ae240..87825cf96f33 100644
--- a/Documentation/process/applying-patches.rst
+++ b/Documentation/process/applying-patches.rst
@@ -9,6 +9,10 @@ Original by:
Last update:
2016-09-14
+.. note::
+
+ This document is obsolete. In most cases, rather than using ``patch``
+ manually, you'll almost certainly want to look at using Git instead.
A frequently asked question on the Linux Kernel Mailing List is how to apply
a patch to the kernel or, more specifically, what base kernel a patch for