From: Junio C Hamano <junio@hera.kernel.org>
Date: Mon, 6 Feb 2006 02:27:38 +0000 (+0000)
Subject: Autogenerated man pages for v1.1.6-g2718
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=3e7beb219d4fefda200adef7153132a327bb3f45;p=git.git

Autogenerated man pages for v1.1.6-g2718
---

diff --git a/man1/git-send-email.1 b/man1/git-send-email.1
index 4b009327b..3f01fce6a 100755
--- a/man1/git-send-email.1
+++ b/man1/git-send-email.1
@@ -23,7 +23,7 @@ git-send-email \- Send a collection of patches as emails
 .SH "SYNOPSIS"
 
 
-git\-send\-email [options] <file|directory> [... file|directory]
+\fIgit\-send\-email\fR [options] <file|directory> [... file|directory]
 
 .SH "DESCRIPTION"
 
@@ -39,33 +39,37 @@ The header of the email is configurable by command line options\&. If not specif
 The options available are:
 
 .TP
-\-\-to
-Specify the primary recipient of the emails generated\&. Generally, this will be the upstream maintainer of the project involved\&.
-
-.TP
-\-\-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\&.
+\-\-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
 
 .TP
 \-\-compose
-Use \\$EDITOR to edit an introductory message for the patch series\&.
+Use $EDITOR to edit an introductory message for the patch series\&.
 
 .TP
-\-\-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\&.
+\-\-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\&.
 
 .TP
 \-\-in\-reply\-to
 Specify the contents of the first In\-Reply\-To header\&. Subsequent emails will refer to the previous email instead of this if \-\-chain\-reply\-to is set (the default) Only necessary if \-\-compose is also set\&. If \-\-compose is not set, this will be prompted for\&.
 
 .TP
-\-\-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\&.
 
 .TP
 \-\-smtp\-server
 If set, specifies the outgoing SMTP server to use\&. Defaults to localhost\&.
 
+.TP
+\-\-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\&.
+
+.TP
+\-\-to
+Specify the primary recipient of the emails generated\&. Generally, this will be the upstream maintainer of the project involved\&.
+
 .SH "AUTHOR"