From 748f0ff5616c08a2616b52923635b7b32d47ae3b Mon Sep 17 00:00:00 2001 From: Julien Olivain Date: Sun, 28 Aug 2022 11:24:30 +0200 Subject: [PATCH] docs/manual: patch subjects shall not be numbered The script "utils/check-package" checks that patch email prefix are not be numbered. See: https://git.buildroot.org/buildroot/tree/utils/checkpackagelib/lib_patch.py?h=2022.08-rc1#n42 The error message recommends to generate patches to be included in Buildroot with the command 'git format-patch -N'. The patch policy section in the Buildroot manual does mention that. This commit adds a note about that requirement. Signed-off-by: Julien Olivain Signed-off-by: Yann E. MORIN (cherry picked from commit 5ac1b1866db3e3e386d609c0f3b502789f6f8da5) Signed-off-by: Peter Korsgaard --- docs/manual/patch-policy.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt index e704a0d3f3..063ef984d8 100644 --- a/docs/manual/patch-policy.txt +++ b/docs/manual/patch-policy.txt @@ -44,6 +44,11 @@ These patch files should be named +-.patch+. - The field ++ in the patch file name refers to the 'apply order', and shall start at 1; It is preferred to pad the number with zeros up to 4 digits, like 'git-format-patch' does. E.g.: +0001-foobar-the-buz.patch+ +- The patch email subject prefix shall not be numbered. Patches shall + be generated with the +git format-patch -N+ command, since this + numbering is automatically added for series. For example, the patch + subject line should look like +Subject: [PATCH] foobar the buz+ rather + than +Subject: [PATCH n/m] foobar the buz+. - Previously, it was mandatory for patches to be prefixed with the name of the package, like +--.patch+, but that is no longer the case. Existing packages will be fixed as time passes. 'Do