Autogenerated HTML docs for v2.29.2-154-g7f7eb

1 files changed, 11 insertions, 10 deletions

diff --git a/MyFirstContribution.html b/MyFirstContribution.html
index 61bc5f4f0..9ad367c9a 100644
--- a/MyFirstContribution.html
+++ b/MyFirstContribution.html
@@ -991,7 +991,7 @@ component you’re working on, followed by a blank line (always required) an
 the body of your commit message, which should provide the bulk of the context.

 Remember to be explicit and provide the "Why" of your change, especially if it

 couldn’t easily be understood from your diff. When editing your commit message,

-don&#8217;t remove the Signed-off-by line which was added by <code>-s</code> above.</p></div>

+don&#8217;t remove the <code>Signed-off-by</code> trailer which was added by <code>-s</code> above.</p></div>

 <div class="listingblock">

 <div class="content">

 <pre><code>psuh: add a built-in by popular demand

@@ -1224,6 +1224,15 @@ your command took arguments. Try to use well-established manpage headers so your
 documentation is consistent with other Git and UNIX manpages; this makes life

 easier for your user, who can skip to the section they know contains the

 information they need.</p></div>

+<div class="admonitionblock">

+<table><tr>

+<td class="icon">

+<div class="title">Note</div>

+</td>

+<td class="content">Before trying to build the docs, make sure you have the package <code>asciidoc</code>

+installed.</td>

+</tr></table>

+</div>

 <div class="paragraph"><p>Now that you&#8217;ve written your manpage, you&#8217;ll need to build it explicitly. We

 convert your AsciiDoc to troff which is man-readable like so:</p></div>

 <div class="listingblock">

@@ -1237,14 +1246,6 @@ $ man Documentation/git-psuh.1</code></pre>
 <pre><code>$ make -C Documentation/ git-psuh.1

 $ man Documentation/git-psuh.1</code></pre>

 </div></div>

-<div class="admonitionblock">

-<table><tr>

-<td class="icon">

-<div class="title">Note</div>

-</td>

-<td class="content">You may need to install the package <code>asciidoc</code> to get this to work.</td>

-</tr></table>

-</div>

 <div class="paragraph"><p>While this isn&#8217;t as satisfying as running through <code>git help</code>, you can at least

 check that your help page looks right.</p></div>

 <div class="paragraph"><p>You can also check that the documentation coverage is good (that is, the project

@@ -1899,7 +1900,7 @@ should generate your diffs from <code>&lt;topic&gt;..&lt;mybranch&gt;</code> and
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-08-27 14:26:53 PDT

+ 2020-11-02 14:02:22 PST

 </div>

 </div>

 </body>