Add subject tag suggestion [fsverity-utils PATCH] to the Contributing section, so that developer can follow this. Signed-off-by: Po-Hsu Lin <po-hsu.lin@xxxxxxxxxxxxx> --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index b11f6d5..5a76247 100644 --- a/README.md +++ b/README.md @@ -136,11 +136,12 @@ Send questions and bug reports to linux-fscrypt@xxxxxxxxxxxxxxx. ## Contributing -Send patches to linux-fscrypt@xxxxxxxxxxxxxxx. Patches should follow -the Linux kernel's coding style. A `.clang-format` file is provided -to approximate this coding style; consider using `git clang-format`. -Additionally, like the Linux kernel itself, patches require the -following "sign-off" procedure: +Send patches to linux-fscrypt@xxxxxxxxxxxxxxx with the additional tag +'fsverity-utils' in the subject, i.e. [fsverity-utils PATCH]. Patches +should follow the Linux kernel's coding style. A `.clang-format` file +is provided to approximate this coding style; consider using + `git clang-format`. Additionally, like the Linux kernel itself, +patches require the following "sign-off" procedure: The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right -- 2.17.1
|