Autogenerated HTML docs for v2.22.0-68-g0aae9

1 files changed, 8 insertions, 2 deletions

diff --git a/git-format-patch.html b/git-format-patch.html
index 0c69c8ed7..fad25ef01 100644
--- a/git-format-patch.html
+++ b/git-format-patch.html
@@ -762,7 +762,8 @@ git-format-patch(1) Manual Page
                    [--rfc] [--subject-prefix=Subject-Prefix]

                    [(--reroll-count|-v) <n>]

                    [--to=<email>] [--cc=<email>]

-                   [--[no-]cover-letter] [--quiet] [--notes[=<ref>]]

+                   [--[no-]cover-letter] [--quiet]

+                   [--no-notes | --notes[=<ref>]]

                    [--interdiff=<previous>]

                    [--range-diff=<previous> [--creation-factor=<percent>]]

                    [--progress]

@@ -1858,6 +1859,9 @@ material (this may change in the future).</p></div>
 <dt class="hdlist1">

 --notes[=&lt;ref&gt;]

 </dt>

+<dt class="hdlist1">

+--no-notes

+</dt>

 <dd>

 <p>

         Append the notes (see <a href="git-notes.html">git-notes(1)</a>) for the commit

@@ -1870,6 +1874,8 @@ these explanations after <code>format-patch</code> has run but before sending,
 keeping them as Git notes allows them to be maintained between versions

 of the patch series (but see the discussion of the <code>notes.rewrite</code>

 configuration options in <a href="git-notes.html">git-notes(1)</a> to use this workflow).</p></div>

+<div class="paragraph"><p>The default is <code>--no-notes</code>, unless the <code>format.notes</code> configuration is

+set.</p></div>

 </dd>

 <dt class="hdlist1">

 --[no-]signature=&lt;signature&gt;

@@ -2411,7 +2417,7 @@ Extract three topmost commits from the current branch and format them
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2019-02-05 15:33:20 PST

+ 2019-06-13 15:06:39 PDT

 </div>

 </div>

 </body>