summaryrefslogtreecommitdiffstats
diff options
authorHauke <anonymous.contributor@example.org>2013-10-31 20:19:10 +0000
committerKonstantin Ryabitsev <konstantin@linuxfoundation.org>2024-10-04 15:47:32 -0400
commita859c5daf45445a5559a750e6bb0f7842e778218 (patch)
tree26fad28e827178a4bd3b7a594e261933dbab8c97
parentf74d3493c897d5abcb3d398b59772e5306d64243 (diff)
downloadbackports-a859c5daf45445a5559a750e6bb0f7842e778218.tar.gz
add Tool prerequests
-rw-r--r--wiki/Documentation_backports_hacking.mediawiki4
1 files changed, 4 insertions, 0 deletions
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki
index 296bd4d..38910c4 100644
--- a/wiki/Documentation_backports_hacking.mediawiki
+++ b/wiki/Documentation_backports_hacking.mediawiki
@@ -14,6 +14,10 @@ This is now in one repository [https://git.kernel.org/cgit/linux/kernel/git/mcgr
You can generate backports based on different trees depending on your needs. We are supporting build based on [https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/ linux-next.git], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ linux.git] and [https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/ linux-stable.git]. You can also generate builds based on your own tree, but then you probably have to patch backports yourself to add support for that.
+= Tool prerequests =
+
+git, python patch and coccinelle are needed to generate a backports release.
+
= Generate new release =
To generate a own backport release based on linux-next you need the following git trees: