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. PR-URL: #32602 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
nodejs · Apr 11, 2020 · 7ae8ce3 · 7ae8ce3
1 parent 655ff39
commit 7ae8ce3
Showing 1 changed file with 2 additions and 2 deletions.
diff --git 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