From f9ca97d6b6efc644961bdfb77047b162bca91919 Mon Sep 17 00:00:00 2001
From: Junio C Hamano <junio@hera.kernel.org>
Date: Tue, 25 Jul 2006 22:23:09 +0000
Subject: [PATCH] Autogenerated HTML docs for v1.4.2-rc2

---
 git-format-patch.html | 29 +++++++++++++++++++++++++++--
 git-format-patch.txt  | 16 +++++++++++++++-
 2 files changed, 42 insertions(+), 3 deletions(-)

diff --git a/git-format-patch.html b/git-format-patch.html
index 9129d8111..5595286ba 100644
--- a/git-format-patch.html
+++ b/git-format-patch.html
@@ -273,8 +273,9 @@ git-format-patch(1) Manual Page
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
-<div class="content"><em>git-format-patch</em> [-n | -k] [-o &lt;dir&gt; | --stdout] [--attach]
+<div class="content"><em>git-format-patch</em> [-n | -k] [-o &lt;dir&gt; | --stdout] [--attach] [--thread]
                    [-s | --signoff] [--diff-options] [--start-number &lt;n&gt;]
+                   [--in-reply-to=Message-Id]
                    &lt;since&gt;[..&lt;until&gt;]</div></div>
 </div>
 <h2>DESCRIPTION</h2>
@@ -293,6 +294,10 @@ output, unless the --stdout option is specified.</p>
 they are created in the current working directory.</p>
 <p>If -n is specified, instead of "[PATCH] Subject", the first line
 is formatted as "[PATCH n/m] Subject".</p>
+<p>If given --thread, git-format-patch will generate In-Reply-To and
+References headers to make the second and subsequent patch mails appear
+as replies to the first mail; this also generates a Message-Id header to
+reference.</p>
 </div>
 <h2>OPTIONS</h2>
 <div class="sectionbody">
@@ -357,6 +362,26 @@ is formatted as "[PATCH n/m] Subject".</p>
         Create attachments instead of inlining patches.
 </p>
 </dd>
+<dt>
+--thread
+</dt>
+<dd>
+<p>
+        Add In-Reply-To and References headers to make the second and
+        subsequent mails appear as replies to the first.  Also generates
+        the Message-Id header to reference.
+</p>
+</dd>
+<dt>
+--in-reply-to=Message-Id
+</dt>
+<dd>
+<p>
+        Make the first mail (or all the mails with --no-thread) appear as a
+        reply to the given Message-Id, which avoids breaking threads to
+        provide a new patch series.
+</p>
+</dd>
 </dl>
 </div>
 <h2>CONFIGURATION</h2>
@@ -425,7 +450,7 @@ git-format-patch -M -B origin
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 15-Jul-2006 01:37:46 UTC
+Last updated 25-Jul-2006 22:23:03 UTC
 </div>
 </div>
 </body>
diff --git a/git-format-patch.txt b/git-format-patch.txt
index 4ca0014da..67425dc03 100644
--- a/git-format-patch.txt
+++ b/git-format-patch.txt
@@ -9,8 +9,9 @@ git-format-patch - Prepare patches for e-mail submission
 SYNOPSIS
 --------
 [verse]
-'git-format-patch' [-n | -k] [-o <dir> | --stdout] [--attach]
+'git-format-patch' [-n | -k] [-o <dir> | --stdout] [--attach] [--thread]
 	           [-s | --signoff] [--diff-options] [--start-number <n>]
+		   [--in-reply-to=Message-Id]
 		   <since>[..<until>]
 
 DESCRIPTION
@@ -35,6 +36,10 @@ they are created in the current working directory.
 If -n is specified, instead of "[PATCH] Subject", the first line
 is formatted as "[PATCH n/m] Subject".
 
+If given --thread, git-format-patch will generate In-Reply-To and
+References headers to make the second and subsequent patch mails appear
+as replies to the first mail; this also generates a Message-Id header to
+reference.
 
 OPTIONS
 -------
@@ -63,6 +68,15 @@ OPTIONS
 --attach::
 	Create attachments instead of inlining patches.
 
+--thread::
+	Add In-Reply-To and References headers to make the second and
+	subsequent mails appear as replies to the first.  Also generates
+	the Message-Id header to reference.
+
+--in-reply-to=Message-Id::
+	Make the first mail (or all the mails with --no-thread) appear as a
+	reply to the given Message-Id, which avoids breaking threads to
+	provide a new patch series.
 
 CONFIGURATION
 -------------
-- 
2.26.2