SubmittingPatches: more up to date information about the patch format

It has not been considered valid to omit the long patch description
for a long time. Try to explain in more detail what the long patch
description is actually expected to contain.

Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
This commit is contained in:
H. Peter Anvin (Intel) 2026-06-11 12:47:32 -07:00
parent 6015afc6d7
commit 018406b870

View file

@ -33,7 +33,7 @@ There are at least two ways to make it right.
at all.
2) Use "diff -up"
Use "diff -up" or "diff -uprN" to create patches.
Signing your work
@ -86,8 +86,10 @@ An example of patch message
From: Random J Developer <random@developer.example.org>
Subject: [PATCH] Short patch description
Long patch description (could be skipped if patch
is trivial enough)
Long patch description:
Explain the problem you are fixing, the consequences of that problem,
and why your patch is the correct way to fix it.
Signed-off-by: Random J Developer <random@developer.example.org>
---