<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 7.0.1" />\r
+<meta name="generator" content="AsciiDoc 7.0.2" />\r
<style type="text/css">\r
/* Debug borders */\r
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {\r
<p>The options available are:</p>\r
<dl>\r
<dt>\r
---to\r
-</dt>\r
-<dd>\r
-<p>\r
- Specify the primary recipient of the emails generated.\r
- Generally, this will be the upstream maintainer of the\r
- project involved.\r
-</p>\r
-</dd>\r
-<dt>\r
---from\r
+--chain-reply-to, --no-chain-reply-to\r
</dt>\r
<dd>\r
<p>\r
- Specify the sender of the emails. This will default to\r
- the value GIT_COMMITTER_IDENT, as returned by "git-var -l".\r
- The user will still be prompted to confirm this entry.\r
+ If this is set, each email will be sent as a reply to the previous\r
+ email sent. If disabled with "--no-chain-reply-to", all emails after\r
+ the first will be sent as replies to the first email sent. When using\r
+ this, it is recommended that the first file given be an overview of the\r
+ entire patch series.\r
+ Default is --chain-reply-to\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- Use \$EDITOR to edit an introductory message for the\r
+ Use $EDITOR to edit an introductory message for the\r
patch series.\r
</p>\r
</dd>\r
<dt>\r
---subject\r
+--from\r
</dt>\r
<dd>\r
<p>\r
- Specify the initial subject of the email thread.\r
- Only necessary if --compose is also set. If --compose\r
- is not set, this will be prompted for.\r
+ Specify the sender of the emails. This will default to\r
+ the value GIT_COMMITTER_IDENT, as returned by "git-var -l".\r
+ The user will still be prompted to confirm this entry.\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
---chain-reply-to, --no-chain-reply-to\r
+--quiet\r
</dt>\r
<dd>\r
<p>\r
- If this is set, each email will be sent as a reply to the previous\r
- email sent. If disabled with "--no-chain-reply-to", all emails after\r
- the first will be sent as replies to the first email sent. When using\r
- this, it is recommended that the first file given be an overview of the\r
- entire patch series.\r
- Default is --chain-reply-to\r
+ Make git-send-email less verbose. One line per email should be\r
+ all that is output.\r
</p>\r
</dd>\r
<dt>\r
localhost.\r
</p>\r
</dd>\r
+<dt>\r
+--subject\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specify the initial subject of the email thread.\r
+ Only necessary if --compose is also set. If --compose\r
+ is not set, this will be prompted for.\r
+</p>\r
+</dd>\r
+<dt>\r
+--to\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specify the primary recipient of the emails generated.\r
+ Generally, this will be the upstream maintainer of the\r
+ project involved.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>Author</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 27-Dec-2005 00:16:40 PDT\r
+Last updated 06-Feb-2006 02:27:00 UTC\r
</div>\r
</div>\r
</body>\r
-------
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
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
------
projects / git.git / commitdiff