From 86f75880b999faec96526606328b9f653e29a6f2 Mon Sep 17 00:00:00 2001
From: Junio C Hamano <junio@hera.kernel.org>
Date: Mon, 6 Feb 2006 02:27:23 +0000
Subject: [PATCH] Autogenerated HTML docs for v1.1.6-g2718

---
 git-send-email.html | 65 ++++++++++++++++++++++++++++++-----------------------
 git-send-email.txt  | 44 +++++++++++++++++++-----------------
 2 files changed, 61 insertions(+), 48 deletions(-)
diff --git a/git-send-email.html b/git-send-email.html
index af79b671..821328c0 100644
--- a/git-send-email.html
+++ b/git-send-email.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -286,23 +286,16 @@ enabled interface to provide the necessary information.</p>
 <p>The options available are:</p>
 <dl>
 <dt>
---to
-</dt>
-<dd>
-<p>
-        Specify the primary recipient of the emails generated.
-        Generally, this will be the upstream maintainer of the
-        project involved.
-</p>
-</dd>
-<dt>
---from
+--chain-reply-to, --no-chain-reply-to
 </dt>
 <dd>
 <p>
-        Specify the sender of the emails.  This will default to
-        the value GIT_COMMITTER_IDENT, as returned by "git-var -l".
-        The user will still be prompted to confirm this entry.
+        If this is set, each email will be sent as a reply to the previous
+        email sent.  If disabled with "--no-chain-reply-to", all emails after
+        the first will be sent as replies to the first email sent.  When using
+        this, it is recommended that the first file given be an overview of the
+        entire patch series.
+        Default is --chain-reply-to
 </p>
 </dd>
 <dt>
@@ -310,18 +303,18 @@ enabled interface to provide the necessary information.</p>
 </dt>
 <dd>
 <p>
-        Use \$EDITOR to edit an introductory message for the
+        Use $EDITOR to edit an introductory message for the
         patch series.
 </p>
 </dd>
 <dt>
---subject
+--from
 </dt>
 <dd>
 <p>
-        Specify the initial subject of the email thread.
-        Only necessary if --compose is also set.  If --compose
-        is not set, this will be prompted for.
+        Specify the sender of the emails.  This will default to
+        the value GIT_COMMITTER_IDENT, as returned by "git-var -l".
+        The user will still be prompted to confirm this entry.
 </p>
 </dd>
 <dt>
@@ -337,16 +330,12 @@ enabled interface to provide the necessary information.</p>
 </p>
 </dd>
 <dt>
---chain-reply-to, --no-chain-reply-to
+--quiet
 </dt>
 <dd>
 <p>
-        If this is set, each email will be sent as a reply to the previous
-        email sent.  If disabled with "--no-chain-reply-to", all emails after
-        the first will be sent as replies to the first email sent.  When using
-        this, it is recommended that the first file given be an overview of the
-        entire patch series.
-        Default is --chain-reply-to
+        Make git-send-email less verbose.  One line per email should be
+        all that is output.
 </p>
 </dd>
 <dt>
@@ -358,6 +347,26 @@ enabled interface to provide the necessary information.</p>
         localhost.
 </p>
 </dd>
+<dt>
+--subject
+</dt>
+<dd>
+<p>
+        Specify the initial subject of the email thread.
+        Only necessary if --compose is also set.  If --compose
+        is not set, this will be prompted for.
+</p>
+</dd>
+<dt>
+--to
+</dt>
+<dd>
+<p>
+        Specify the primary recipient of the emails generated.
+        Generally, this will be the upstream maintainer of the
+        project involved.
+</p>
+</dd>
 </dl>
 </div>
 <h2>Author</h2>
@@ -376,7 +385,7 @@ send_lots_of_email.pl by Greg Kroah-Hartman.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 27-Dec-2005 00:16:40 PDT
+Last updated 06-Feb-2006 02:27:00 UTC
 </div>
 </div>
 </body>
diff --git a/git-send-email.txt b/git-send-email.txt
index b9bec55e..00537d89 100644
--- a/git-send-email.txt
+++ b/git-send-email.txt
@@ -24,25 +24,23 @@ OPTIONS
 -------
 The options available are:
 
---to::
-	Specify the primary recipient of the emails generated.
-	Generally, this will be the upstream maintainer of the
-	project involved.
+--chain-reply-to, --no-chain-reply-to::
+	If this is set, each email will be sent as a reply to the previous
+	email sent.  If disabled with "--no-chain-reply-to", all emails after
+	the first will be sent as replies to the first email sent.  When using
+	this, it is recommended that the first file given be an overview of the
+	entire patch series.
+	Default is --chain-reply-to
+
+--compose::
+	Use $EDITOR to edit an introductory message for the
+	patch series.
 
 --from::
 	Specify the sender of the emails.  This will default to
 	the value GIT_COMMITTER_IDENT, as returned by "git-var -l".
 	The user will still be prompted to confirm this entry.
 
---compose::
-	Use \$EDITOR to edit an introductory message for the
-	patch series.
-
---subject::
-   	Specify the initial subject of the email thread.
-	Only necessary if --compose is also set.  If --compose
-	is not set, this will be prompted for.
-
 --in-reply-to::
 	Specify the contents of the first In-Reply-To header.
 	Subsequent emails will refer to the previous email 
@@ -50,18 +48,24 @@ The options available are:
 	Only necessary if --compose is also set.  If --compose
 	is not set, this will be prompted for.
 
---chain-reply-to, --no-chain-reply-to::
-	If this is set, each email will be sent as a reply to the previous
-	email sent.  If disabled with "--no-chain-reply-to", all emails after
-	the first will be sent as replies to the first email sent.  When using
-	this, it is recommended that the first file given be an overview of the
-	entire patch series.
-	Default is --chain-reply-to
+--quiet::
+	Make git-send-email less verbose.  One line per email should be
+	all that is output.
 
 --smtp-server::
 	If set, specifies the outgoing SMTP server to use.  Defaults to
 	localhost.
 
+--subject::
+   	Specify the initial subject of the email thread.
+	Only necessary if --compose is also set.  If --compose
+	is not set, this will be prompted for.
+
+--to::
+	Specify the primary recipient of the emails generated.
+	Generally, this will be the upstream maintainer of the
+	project involved.
+
 
 Author
 ------
-- 
2.11.0

