It makes parsing them more difficult.

Signed-off-by: Ben Pfaff <[email protected]>
---
 Documentation/internals/contributing/submitting-patches.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/internals/contributing/submitting-patches.rst 
b/Documentation/internals/contributing/submitting-patches.rst
index 1755c8a6691a..5a314cc60aa7 100644
--- a/Documentation/internals/contributing/submitting-patches.rst
+++ b/Documentation/internals/contributing/submitting-patches.rst
@@ -145,6 +145,9 @@ The description ends with a series of tags, written one to 
a line as the last
 paragraph of the email.  Each tag indicates some property of the patch in an
 easily machine-parseable manner.
 
+Please don't wrap a tag across multiple lines.  If necessary, it's OK to have a
+tag extend beyond the customary maximum width of a commit message.
+
 Examples of common tags follow.
 
 ``Signed-off-by: Author Name <[email protected]...>``
-- 
2.16.1

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to