OpenIPC
/
wiki
mirror of https://github.com/OpenIPC/wiki.git
1
0
Fork 0
Code Activity

wording, markdown formatting.

pull/23/head
Paul Philippov 2022-07-03 18:33:07 -04:00
parent b4dc5850ab
commit dc26df6eb3
1 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
en/integration-kernel.md
View File

@ -1,4 +1,5 @@
# OpenIPC Wiki
[Table of Content](../index.md)
Additional requirements for kernel configuration
@ -16,11 +17,19 @@ CONFIG_IP_PNP_DHCP=y
CONFIG_ROOT_NFS=y
```
## Patch files
## Patch file requirements
Patch files should be named `<number>-<description>.patch`.
- The patch files should not contain any package version reference in their filename.
- The field `<number>` 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_
- A message explaining what the patch does, and why it is needed, should be added in the header commentary of the patch.
- You should add a Signed-off-by statement in the header of each patch to help with keeping track of the changes and to certify that the patch is released under the same license as the software that is modified.
- Patch file name should follow format `<number>-<description>.patch`.
- Patch file should not contain any reference to package version in its name.
- The `<number>` part of patch's file name refers to the application order
starting from 1. It is preferred to left-pad the number with zeros up to total
of four digits, like `git-format-patch` does. _0001-foobar-the-buz.patch_
- Patch file should contain a commentary in its header, explaining what this
patch does, and why it is needed.
- Add a _Signed-off-by_ statement in the header of each patch file to help
tracking changes and certify that the patch is released under the same license
as the software it modifies.