Przeglądaj źródła

docs/manual: fix patch naming convention

Otherwise conflicts with the naming convention from previous section.

Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Gary Bisson 9 lat temu
rodzic
commit
fe7babeeb0
1 zmienionych plików z 4 dodań i 4 usunięć
  1. 4 4
      docs/manual/patch-policy.txt

+ 4 - 4
docs/manual/patch-policy.txt

@@ -73,12 +73,12 @@ details.
 * If a +series+ file exists in the package directory, then patches are
 * If a +series+ file exists in the package directory, then patches are
   applied according to the +series+ file;
   applied according to the +series+ file;
 +
 +
-* Otherwise, patch files matching +<packagename>-*.patch+
-  are applied in alphabetical order.
+* Otherwise, patch files matching +*.patch+ are applied in alphabetical
+  order.
   So, to ensure they are applied in the right order, it is highly
   So, to ensure they are applied in the right order, it is highly
   recommended to name the patch files like this:
   recommended to name the patch files like this:
-  +<packagename>-<number>-<description>.patch+, where +<number>+
-  refers to the 'apply order'.
+  +<number>-<description>.patch+, where +<number>+ refers to the
+  'apply order'.
 
 
 . If +BR2_GLOBAL_PATCH_DIR+ is defined, the directories will be
 . If +BR2_GLOBAL_PATCH_DIR+ is defined, the directories will be
   enumerated in the order they are specified. The patches are applied
   enumerated in the order they are specified. The patches are applied