Autogenerated HTML docs for v1.8.0-197-g5a907

1 files changed, 18 insertions, 2 deletions

diff --git a/git-format-patch.html b/git-format-patch.html
index d1d06f724..60107a5c5 100644
--- a/git-format-patch.html
+++ b/git-format-patch.html
@@ -594,7 +594,7 @@ git-format-patch(1) Manual Page
                    [--ignore-if-in-upstream]

                    [--subject-prefix=Subject-Prefix]

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

-                   [--cover-letter] [--quiet]

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

                    [<common diff options>]

                    [ &lt;since&gt; | &lt;revision range&gt; ]</div>

 <div class="verseblock-attribution">

@@ -1351,6 +1351,22 @@ will want to ensure that threading is disabled for <tt>git send-email</tt>.</p><
 </p>

 </dd>

 <dt class="hdlist1">

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

+</dt>

+<dd>

+<p>

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

+        after the three-dash line.

+</p>

+<div class="paragraph"><p>The expected use case of this is to write supporting explanation for

+the commit that does not belong to the commit log message proper,

+and include it with the patch submission. While one can simply write

+these explanations after <tt>format-patch</tt> 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 <tt>notes.rewrite</tt>

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

+</dd>

+<dt class="hdlist1">

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

 </dt>

 <dd>

@@ -1771,7 +1787,7 @@ as e-mailable patches:
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2012-09-17 16:55:59 PDT

+Last updated 2012-11-15 13:11:54 PDT

 </div>

 </div>

 </body>