docs/manual/patch-policy.txt

4 [[patch-policy]]
9 necessary to patch the source of the software to get it cross-built within
13 the builds. It supports three ways of applying patch sets: downloaded patches,
15 global patch directory.
21 If it is necessary to apply a patch that is available for download, then add it
23 then Buildroot will assume it is a full URL and download the patch
24 from this location. Otherwise, Buildroot will assume that the patch should be
25 downloaded from +<packagename>_SITE+. It can be a single patch,
26 or a tarball containing a patch series.
39 These patch files should be named +<number>-<description>.patch+.
42 - The patch files coming with Buildroot should not contain any package version
44 - The field +<number>+ in the patch file name refers to the 'apply order',
46   digits, like 'git-format-patch' does. E.g.: +0001-foobar-the-buz.patch+
48   the package, like +<package>-<number>-<description>.patch+, but that is
52   the package directory. In that case, the +series+ file defines the patch
57 ==== Global patch directory
64 [[patch-apply-order]]
74 . If there are some +*.patch+ files in the package's Buildroot
81 * Otherwise, patch files matching +*.patch+ are applied in alphabetical
84   recommended to name the patch files like this:
85   +<number>-<description>.patch+, where +<number>+ refers to the
101 A message explaining what the patch does, and why it is needed, should
102 be added in the header commentary of the patch.
105 patch to help with keeping track of the changes and to certify that the
106 patch is released under the same license as the software that is modified.
109 upstream SCM software to generate the patch set.
114 If you update an existing patch (e.g. when bumping the package version),
116 removed, but do update the rest of the patch comment when appropriate.
118 At the end, the patch should look like:
144 When integrating a patch of which you are not the author, you have to
145 add a few things in the header of the patch itself.
147 Depending on whether the patch has been obtained from the project
161 It is also sensible to add a few words about any changes to the patch