From 086da620defb3bb6716b2b306fe8909b890e03ef Mon Sep 17 00:00:00 2001 From: Sam Roberts Date: Wed, 1 Apr 2020 14:21:21 -0700 Subject: [PATCH] doc: make openssl commit messages be valid The current commit message is wrapped at 80 columns, but commit message descriptions should wrap at 72, so the maintainer has to fix the message up instead of just copying it in. They might not notice that requirement, in which case it has to be fixed during landing because `git node land` notices. To prevent that, make the message template wrap before 72 to keep the landing process as simple as possible. --- doc/guides/maintaining-openssl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/maintaining-openssl.md b/doc/guides/maintaining-openssl.md index bc17c1cc208b5e..a9d752d97d9cbc 100644 --- a/doc/guides/maintaining-openssl.md +++ b/doc/guides/maintaining-openssl.md @@ -93,8 +93,8 @@ The commit message can be (with the openssl version set to the relevant value): ```text deps: update archs files for OpenSSL-1.1.0 - After an OpenSSL source update, all the config files need to be regenerated and - committed by: + After an OpenSSL source update, all the config files need to be + regenerated and committed by: $ cd deps/openssl/config $ make $ git add deps/openssl/config/archs