Autogenerated HTML docs for v2.31.1-442-g7e391

1 files changed, 8 insertions, 5 deletions

diff --git a/SubmittingPatches.html b/SubmittingPatches.html
index 9ef70702a..f4f59235a 100644
--- a/SubmittingPatches.html
+++ b/SubmittingPatches.html
@@ -862,10 +862,13 @@ githooks.txt: improve the intro section
 </ul></div>

 <div class="paragraph"><p>If in doubt which identifier to use, run <code>git log --no-merges</code> on the

 files you are modifying to see the current conventions.</p></div>

-<div class="paragraph" id="summary-section"><p>It&#8217;s customary to start the remainder of the first line after "area: "

-with a lower-case letter. E.g. "doc: clarify&#8230;", not "doc:

-Clarify&#8230;", or "githooks.txt: improve&#8230;", not "githooks.txt:

-Improve&#8230;".</p></div>

+<div class="paragraph" id="summary-section"><p>The title sentence after the "area:" prefix omits the full stop at the

+end, and its first word is not capitalized unless there is a reason to

+capitalize it other than because it is the first word in the sentence.

+E.g. "doc: clarify&#8230;", not "doc: Clarify&#8230;", or "githooks.txt:

+improve&#8230;", not "githooks.txt: Improve&#8230;".  But "refs: HEAD is also

+treated as a ref" is correct, as we spell <code>HEAD</code> in all caps even when

+it appears in the middle of a sentence.</p></div>

 <div class="paragraph" id="meaningful-message"><p>The body should provide a meaningful commit message, which:</p></div>

 <div class="olist arabic"><ol class="arabic">

 <li>

@@ -1393,7 +1396,7 @@ this problem around.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2021-03-17 15:51:21 PDT

+ 2021-04-30 15:03:36 JST

 </div>

 </div>

 </body>