Home Home > GIT Browse
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Zimmermann <tzimmermann@suse.de>2018-10-11 15:46:10 +0200
committerThomas Zimmermann <tzimmermann@suse.de>2018-10-12 12:26:54 +0200
commitc50f97b8c49ab7161c135ab841c819a0d1711749 (patch)
tree10e7a0e650a37aa360f60e244cc78fa1c19094f4
parent1d17b6db6fa50bd18e7296cc6e69bdc33890f339 (diff)
Update documentation wrt. Patch-mainline
Common practice is to set Patch-mainline to a Linux release tag. More than 95% of all patches follow this convention. The remaining 5% have been fixed accordingly in SLE15. The documentation is inconsistent wrt. to the content of Patch-mainline. In some places it refers to a release tag, in others it refers to a version number. With this cleanup, documentation in scripts/ refers to release tags. This change is a follow-up for commit 1d81d2699cd3.
-rw-r--r--scripts/patch-tag-template2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/patch-tag-template b/scripts/patch-tag-template
index 4d6650ca9e..353552327e 100644
--- a/scripts/patch-tag-template
+++ b/scripts/patch-tag-template
@@ -38,7 +38,7 @@ Acked-by:
# examples:
# Patch-mainline: never. fixes bugs in SUSE specific code
# Patch-mainline: submitted 2004-11-01
-# Patch-mainline: 2.6.10-rc1 any free form text is valid after the version
+# Patch-mainline: v2.6.10-rc1 any free form text is valid after the version
#
Patch-mainline: