Autogenerated HTML docs for v1.7.6-rc1
[git/jnareb-git.git] / git-send-email.html
blobec5ef2434b7dde8d0e32a54b60b70c7ab3a810e1
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4 <head>
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <meta name="generator" content="AsciiDoc 8.4.5" />
7 <title>git-send-email(1)</title>
8 <style type="text/css">
9 /* Debug borders */
10 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
12 border: 1px solid red;
16 body {
17 margin: 1em 5% 1em 5%;
20 a {
21 color: blue;
22 text-decoration: underline;
24 a:visited {
25 color: fuchsia;
28 em {
29 font-style: italic;
30 color: navy;
33 strong {
34 font-weight: bold;
35 color: #083194;
38 tt {
39 color: navy;
42 h1, h2, h3, h4, h5, h6 {
43 color: #527bbd;
44 font-family: sans-serif;
45 margin-top: 1.2em;
46 margin-bottom: 0.5em;
47 line-height: 1.3;
50 h1, h2, h3 {
51 border-bottom: 2px solid silver;
53 h2 {
54 padding-top: 0.5em;
56 h3 {
57 float: left;
59 h3 + * {
60 clear: left;
63 div.sectionbody {
64 font-family: serif;
65 margin-left: 0;
68 hr {
69 border: 1px solid silver;
72 p {
73 margin-top: 0.5em;
74 margin-bottom: 0.5em;
77 ul, ol, li > p {
78 margin-top: 0;
81 pre {
82 padding: 0;
83 margin: 0;
86 span#author {
87 color: #527bbd;
88 font-family: sans-serif;
89 font-weight: bold;
90 font-size: 1.1em;
92 span#email {
94 span#revnumber, span#revdate, span#revremark {
95 font-family: sans-serif;
98 div#footer {
99 font-family: sans-serif;
100 font-size: small;
101 border-top: 2px solid silver;
102 padding-top: 0.5em;
103 margin-top: 4.0em;
105 div#footer-text {
106 float: left;
107 padding-bottom: 0.5em;
109 div#footer-badges {
110 float: right;
111 padding-bottom: 0.5em;
114 div#preamble {
115 margin-top: 1.5em;
116 margin-bottom: 1.5em;
118 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
119 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
120 div.admonitionblock {
121 margin-top: 1.5em;
122 margin-bottom: 1.5em;
124 div.admonitionblock {
125 margin-top: 2.5em;
126 margin-bottom: 2.5em;
129 div.content { /* Block element content. */
130 padding: 0;
133 /* Block element titles. */
134 div.title, caption.title {
135 color: #527bbd;
136 font-family: sans-serif;
137 font-weight: bold;
138 text-align: left;
139 margin-top: 1.0em;
140 margin-bottom: 0.5em;
142 div.title + * {
143 margin-top: 0;
146 td div.title:first-child {
147 margin-top: 0.0em;
149 div.content div.title:first-child {
150 margin-top: 0.0em;
152 div.content + div.title {
153 margin-top: 0.0em;
156 div.sidebarblock > div.content {
157 background: #ffffee;
158 border: 1px solid silver;
159 padding: 0.5em;
162 div.listingblock > div.content {
163 border: 1px solid silver;
164 background: #f4f4f4;
165 padding: 0.5em;
168 div.quoteblock {
169 padding-left: 2.0em;
170 margin-right: 10%;
172 div.quoteblock > div.attribution {
173 padding-top: 0.5em;
174 text-align: right;
177 div.verseblock {
178 padding-left: 2.0em;
179 margin-right: 10%;
181 div.verseblock > div.content {
182 white-space: pre;
184 div.verseblock > div.attribution {
185 padding-top: 0.75em;
186 text-align: left;
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
189 div.verseblock + div.attribution {
190 text-align: left;
193 div.admonitionblock .icon {
194 vertical-align: top;
195 font-size: 1.1em;
196 font-weight: bold;
197 text-decoration: underline;
198 color: #527bbd;
199 padding-right: 0.5em;
201 div.admonitionblock td.content {
202 padding-left: 0.5em;
203 border-left: 2px solid silver;
206 div.exampleblock > div.content {
207 border-left: 2px solid silver;
208 padding: 0.5em;
211 div.imageblock div.content { padding-left: 0; }
212 span.image img { border-style: none; }
213 a.image:visited { color: white; }
215 dl {
216 margin-top: 0.8em;
217 margin-bottom: 0.8em;
219 dt {
220 margin-top: 0.5em;
221 margin-bottom: 0;
222 font-style: normal;
223 color: navy;
225 dd > *:first-child {
226 margin-top: 0.1em;
229 ul, ol {
230 list-style-position: outside;
232 ol.arabic {
233 list-style-type: decimal;
235 ol.loweralpha {
236 list-style-type: lower-alpha;
238 ol.upperalpha {
239 list-style-type: upper-alpha;
241 ol.lowerroman {
242 list-style-type: lower-roman;
244 ol.upperroman {
245 list-style-type: upper-roman;
248 div.compact ul, div.compact ol,
249 div.compact p, div.compact p,
250 div.compact div, div.compact div {
251 margin-top: 0.1em;
252 margin-bottom: 0.1em;
255 div.tableblock > table {
256 border: 3px solid #527bbd;
258 thead {
259 font-family: sans-serif;
260 font-weight: bold;
262 tfoot {
263 font-weight: bold;
265 td > div.verse {
266 white-space: pre;
268 p.table {
269 margin-top: 0;
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
272 div.tableblock > table[frame="void"] {
273 border-style: none;
275 div.tableblock > table[frame="hsides"] {
276 border-left-style: none;
277 border-right-style: none;
279 div.tableblock > table[frame="vsides"] {
280 border-top-style: none;
281 border-bottom-style: none;
285 div.hdlist {
286 margin-top: 0.8em;
287 margin-bottom: 0.8em;
289 div.hdlist tr {
290 padding-bottom: 15px;
292 dt.hdlist1.strong, td.hdlist1.strong {
293 font-weight: bold;
295 td.hdlist1 {
296 vertical-align: top;
297 font-style: normal;
298 padding-right: 0.8em;
299 color: navy;
301 td.hdlist2 {
302 vertical-align: top;
304 div.hdlist.compact tr {
305 margin: 0;
306 padding-bottom: 0;
309 .comment {
310 background: yellow;
313 @media print {
314 div#footer-badges { display: none; }
317 div#toctitle {
318 color: #527bbd;
319 font-family: sans-serif;
320 font-size: 1.1em;
321 font-weight: bold;
322 margin-top: 1.0em;
323 margin-bottom: 0.1em;
326 div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
327 margin-top: 0;
328 margin-bottom: 0;
330 div.toclevel2 {
331 margin-left: 2em;
332 font-size: 0.9em;
334 div.toclevel3 {
335 margin-left: 4em;
336 font-size: 0.9em;
338 div.toclevel4 {
339 margin-left: 6em;
340 font-size: 0.9em;
342 /* Overrides for manpage documents */
343 h1 {
344 padding-top: 0.5em;
345 padding-bottom: 0.5em;
346 border-top: 2px solid silver;
347 border-bottom: 2px solid silver;
349 h2 {
350 border-style: none;
352 div.sectionbody {
353 margin-left: 5%;
356 @media print {
357 div#toc { display: none; }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
362 div.sidebar-content {
363 background: #ffffee;
364 border: 1px solid silver;
365 padding: 0.5em;
367 div.sidebar-title, div.image-title {
368 color: #527bbd;
369 font-family: sans-serif;
370 font-weight: bold;
371 margin-top: 0.0em;
372 margin-bottom: 0.5em;
375 div.listingblock div.content {
376 border: 1px solid silver;
377 background: #f4f4f4;
378 padding: 0.5em;
381 div.quoteblock-attribution {
382 padding-top: 0.5em;
383 text-align: right;
386 div.verseblock-content {
387 white-space: pre;
389 div.verseblock-attribution {
390 padding-top: 0.75em;
391 text-align: left;
394 div.exampleblock-content {
395 border-left: 2px solid silver;
396 padding-left: 0.5em;
399 /* IE6 sets dynamically generated links as visited. */
400 div#toc a:visited { color: blue; }
401 </style>
402 </head>
403 <body>
404 <div id="header">
405 <h1>
406 git-send-email(1) Manual Page
407 </h1>
408 <h2>NAME</h2>
409 <div class="sectionbody">
410 <p>git-send-email -
411 Send a collection of patches as emails
412 </p>
413 </div>
414 </div>
415 <h2 id="_synopsis">SYNOPSIS</h2>
416 <div class="sectionbody">
417 <div class="paragraph"><p><em>git send-email</em> [options] &lt;file|directory|rev-list options&gt;&#8230;</p></div>
418 </div>
419 <h2 id="_description">DESCRIPTION</h2>
420 <div class="sectionbody">
421 <div class="paragraph"><p>Takes the patches given on the command line and emails them out.
422 Patches can be specified as files, directories (which will send all
423 files in the directory), or directly as a revision list. In the
424 last case, any format accepted by <a href="git-format-patch.html">git-format-patch(1)</a> can
425 be passed to git send-email.</p></div>
426 <div class="paragraph"><p>The header of the email is configurable by command line options. If not
427 specified on the command line, the user will be prompted with a ReadLine
428 enabled interface to provide the necessary information.</p></div>
429 <div class="paragraph"><p>There are two formats accepted for patch files:</p></div>
430 <div class="olist arabic"><ol class="arabic">
431 <li>
433 mbox format files
434 </p>
435 <div class="paragraph"><p>This is what <a href="git-format-patch.html">git-format-patch(1)</a> generates. Most headers and MIME
436 formatting are ignored.</p></div>
437 </li>
438 <li>
440 The original format used by Greg Kroah-Hartman&#8217;s <em>send_lots_of_email.pl</em>
441 script
442 </p>
443 <div class="paragraph"><p>This format expects the first line of the file to contain the "Cc:" value
444 and the "Subject:" of the message as the second line.</p></div>
445 </li>
446 </ol></div>
447 </div>
448 <h2 id="_options">OPTIONS</h2>
449 <div class="sectionbody">
450 <h3 id="_composing">Composing</h3><div style="clear:left"></div>
451 <div class="dlist"><dl>
452 <dt class="hdlist1">
453 --annotate
454 </dt>
455 <dd>
457 Review and edit each patch you&#8217;re about to send. See the
458 CONFIGURATION section for <em>sendemail.multiedit</em>.
459 </p>
460 </dd>
461 <dt class="hdlist1">
462 --bcc=&lt;address&gt;
463 </dt>
464 <dd>
466 Specify a "Bcc:" value for each email. Default is the value of
467 <em>sendemail.bcc</em>.
468 </p>
469 <div class="paragraph"><p>The --bcc option must be repeated for each user you want on the bcc list.</p></div>
470 </dd>
471 <dt class="hdlist1">
472 --cc=&lt;address&gt;
473 </dt>
474 <dd>
476 Specify a starting "Cc:" value for each email.
477 Default is the value of <em>sendemail.cc</em>.
478 </p>
479 <div class="paragraph"><p>The --cc option must be repeated for each user you want on the cc list.</p></div>
480 </dd>
481 <dt class="hdlist1">
482 --compose
483 </dt>
484 <dd>
486 Invoke a text editor (see GIT_EDITOR in <a href="git-var.html">git-var(1)</a>)
487 to edit an introductory message for the patch series.
488 </p>
489 <div class="paragraph"><p>When <em>--compose</em> is used, git send-email will use the From, Subject, and
490 In-Reply-To headers specified in the message. If the body of the message
491 (what you type after the headers and a blank line) only contains blank
492 (or GIT: prefixed) lines the summary won&#8217;t be sent, but From, Subject,
493 and In-Reply-To headers will be used unless they are removed.</p></div>
494 <div class="paragraph"><p>Missing From or In-Reply-To headers will be prompted for.</p></div>
495 <div class="paragraph"><p>See the CONFIGURATION section for <em>sendemail.multiedit</em>.</p></div>
496 </dd>
497 <dt class="hdlist1">
498 --from=&lt;address&gt;
499 </dt>
500 <dd>
502 Specify the sender of the emails. If not specified on the command line,
503 the value of the <em>sendemail.from</em> configuration option is used. If
504 neither the command line option nor <em>sendemail.from</em> are set, then the
505 user will be prompted for the value. The default for the prompt will be
506 the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not
507 set, as returned by "git var -l".
508 </p>
509 </dd>
510 <dt class="hdlist1">
511 --in-reply-to=&lt;identifier&gt;
512 </dt>
513 <dd>
515 Make the first mail (or all the mails with <tt>--no-thread</tt>) appear as a
516 reply to the given Message-Id, which avoids breaking threads to
517 provide a new patch series.
518 The second and subsequent emails will be sent as replies according to
519 the <tt>--[no]-chain-reply-to</tt> setting.
520 </p>
521 <div class="paragraph"><p>So for example when <tt>--thread</tt> and <tt>--no-chain-reply-to</tt> are specified, the
522 second and subsequent patches will be replies to the first one like in the
523 illustration below where <tt>[PATCH v2 0/3]</tt> is in reply to <tt>[PATCH 0/2]</tt>:</p></div>
524 <div class="literalblock">
525 <div class="content">
526 <pre><tt>[PATCH 0/2] Here is what I did...
527 [PATCH 1/2] Clean up and tests
528 [PATCH 2/2] Implementation
529 [PATCH v2 0/3] Here is a reroll
530 [PATCH v2 1/3] Clean up
531 [PATCH v2 2/3] New tests
532 [PATCH v2 3/3] Implementation</tt></pre>
533 </div></div>
534 <div class="paragraph"><p>Only necessary if --compose is also set. If --compose
535 is not set, this will be prompted for.</p></div>
536 </dd>
537 <dt class="hdlist1">
538 --subject=&lt;string&gt;
539 </dt>
540 <dd>
542 Specify the initial subject of the email thread.
543 Only necessary if --compose is also set. If --compose
544 is not set, this will be prompted for.
545 </p>
546 </dd>
547 <dt class="hdlist1">
548 --to=&lt;address&gt;
549 </dt>
550 <dd>
552 Specify the primary recipient of the emails generated. Generally, this
553 will be the upstream maintainer of the project involved. Default is the
554 value of the <em>sendemail.to</em> configuration value; if that is unspecified,
555 and --to-cmd is not specified, this will be prompted for.
556 </p>
557 <div class="paragraph"><p>The --to option must be repeated for each user you want on the to list.</p></div>
558 </dd>
559 <dt class="hdlist1">
560 --8bit-encoding=&lt;encoding&gt;
561 </dt>
562 <dd>
564 When encountering a non-ASCII message or subject that does not
565 declare its encoding, add headers/quoting to indicate it is
566 encoded in &lt;encoding&gt;. Default is the value of the
567 <em>sendemail.assume8bitEncoding</em>; if that is unspecified, this
568 will be prompted for if any non-ASCII files are encountered.
569 </p>
570 <div class="paragraph"><p>Note that no attempts whatsoever are made to validate the encoding.</p></div>
571 </dd>
572 </dl></div>
573 <h3 id="_sending">Sending</h3><div style="clear:left"></div>
574 <div class="dlist"><dl>
575 <dt class="hdlist1">
576 --envelope-sender=&lt;address&gt;
577 </dt>
578 <dd>
580 Specify the envelope sender used to send the emails.
581 This is useful if your default address is not the address that is
582 subscribed to a list. In order to use the <em>From</em> address, set the
583 value to "auto". If you use the sendmail binary, you must have
584 suitable privileges for the -f parameter. Default is the value of the
585 <em>sendemail.envelopesender</em> configuration variable; if that is
586 unspecified, choosing the envelope sender is left to your MTA.
587 </p>
588 </dd>
589 <dt class="hdlist1">
590 --smtp-encryption=&lt;encryption&gt;
591 </dt>
592 <dd>
594 Specify the encryption to use, either <em>ssl</em> or <em>tls</em>. Any other
595 value reverts to plain SMTP. Default is the value of
596 <em>sendemail.smtpencryption</em>.
597 </p>
598 </dd>
599 <dt class="hdlist1">
600 --smtp-domain=&lt;FQDN&gt;
601 </dt>
602 <dd>
604 Specifies the Fully Qualified Domain Name (FQDN) used in the
605 HELO/EHLO command to the SMTP server. Some servers require the
606 FQDN to match your IP address. If not set, git send-email attempts
607 to determine your FQDN automatically. Default is the value of
608 <em>sendemail.smtpdomain</em>.
609 </p>
610 </dd>
611 <dt class="hdlist1">
612 --smtp-pass[=&lt;password&gt;]
613 </dt>
614 <dd>
616 Password for SMTP-AUTH. The argument is optional: If no
617 argument is specified, then the empty string is used as
618 the password. Default is the value of <em>sendemail.smtppass</em>,
619 however <em>--smtp-pass</em> always overrides this value.
620 </p>
621 <div class="paragraph"><p>Furthermore, passwords need not be specified in configuration files
622 or on the command line. If a username has been specified (with
623 <em>--smtp-user</em> or a <em>sendemail.smtpuser</em>), but no password has been
624 specified (with <em>--smtp-pass</em> or <em>sendemail.smtppass</em>), then the
625 user is prompted for a password while the input is masked for privacy.</p></div>
626 </dd>
627 <dt class="hdlist1">
628 --smtp-server=&lt;host&gt;
629 </dt>
630 <dd>
632 If set, specifies the outgoing SMTP server to use (e.g.
633 <tt>smtp.example.com</tt> or a raw IP address). Alternatively it can
634 specify a full pathname of a sendmail-like program instead;
635 the program must support the <tt>-i</tt> option. Default value can
636 be specified by the <em>sendemail.smtpserver</em> configuration
637 option; the built-in default is <tt>/usr/sbin/sendmail</tt> or
638 <tt>/usr/lib/sendmail</tt> if such program is available, or
639 <tt>localhost</tt> otherwise.
640 </p>
641 </dd>
642 <dt class="hdlist1">
643 --smtp-server-port=&lt;port&gt;
644 </dt>
645 <dd>
647 Specifies a port different from the default port (SMTP
648 servers typically listen to smtp port 25, but may also listen to
649 submission port 587, or the common SSL smtp port 465);
650 symbolic port names (e.g. "submission" instead of 587)
651 are also accepted. The port can also be set with the
652 <em>sendemail.smtpserverport</em> configuration variable.
653 </p>
654 </dd>
655 <dt class="hdlist1">
656 --smtp-server-option=&lt;option&gt;
657 </dt>
658 <dd>
660 If set, specifies the outgoing SMTP server option to use.
661 Default value can be specified by the <em>sendemail.smtpserveroption</em>
662 configuration option.
663 </p>
664 <div class="paragraph"><p>The --smtp-server-option option must be repeated for each option you want
665 to pass to the server. Likewise, different lines in the configuration files
666 must be used for each option.</p></div>
667 </dd>
668 <dt class="hdlist1">
669 --smtp-ssl
670 </dt>
671 <dd>
673 Legacy alias for <em>--smtp-encryption ssl</em>.
674 </p>
675 </dd>
676 <dt class="hdlist1">
677 --smtp-user=&lt;user&gt;
678 </dt>
679 <dd>
681 Username for SMTP-AUTH. Default is the value of <em>sendemail.smtpuser</em>;
682 if a username is not specified (with <em>--smtp-user</em> or <em>sendemail.smtpuser</em>),
683 then authentication is not attempted.
684 </p>
685 </dd>
686 </dl></div>
687 <h3 id="_automating">Automating</h3><div style="clear:left"></div>
688 <div class="dlist"><dl>
689 <dt class="hdlist1">
690 --to-cmd=&lt;command&gt;
691 </dt>
692 <dd>
694 Specify a command to execute once per patch file which
695 should generate patch file specific "To:" entries.
696 Output of this command must be single email address per line.
697 Default is the value of <em>sendemail.tocmd</em> configuration value.
698 </p>
699 </dd>
700 <dt class="hdlist1">
701 --cc-cmd=&lt;command&gt;
702 </dt>
703 <dd>
705 Specify a command to execute once per patch file which
706 should generate patch file specific "Cc:" entries.
707 Output of this command must be single email address per line.
708 Default is the value of <em>sendemail.cccmd</em> configuration value.
709 </p>
710 </dd>
711 <dt class="hdlist1">
712 --[no-]chain-reply-to
713 </dt>
714 <dd>
716 If this is set, each email will be sent as a reply to the previous
717 email sent. If disabled with "--no-chain-reply-to", all emails after
718 the first will be sent as replies to the first email sent. When using
719 this, it is recommended that the first file given be an overview of the
720 entire patch series. Disabled by default, but the <em>sendemail.chainreplyto</em>
721 configuration variable can be used to enable it.
722 </p>
723 </dd>
724 <dt class="hdlist1">
725 --identity=&lt;identity&gt;
726 </dt>
727 <dd>
729 A configuration identity. When given, causes values in the
730 <em>sendemail.&lt;identity&gt;</em> subsection to take precedence over
731 values in the <em>sendemail</em> section. The default identity is
732 the value of <em>sendemail.identity</em>.
733 </p>
734 </dd>
735 <dt class="hdlist1">
736 --[no-]signed-off-by-cc
737 </dt>
738 <dd>
740 If this is set, add emails found in Signed-off-by: or Cc: lines to the
741 cc list. Default is the value of <em>sendemail.signedoffbycc</em> configuration
742 value; if that is unspecified, default to --signed-off-by-cc.
743 </p>
744 </dd>
745 <dt class="hdlist1">
746 --suppress-cc=&lt;category&gt;
747 </dt>
748 <dd>
750 Specify an additional category of recipients to suppress the
751 auto-cc of:
752 </p>
753 <div class="ulist"><ul>
754 <li>
756 <em>author</em> will avoid including the patch author
757 </p>
758 </li>
759 <li>
761 <em>self</em> will avoid including the sender
762 </p>
763 </li>
764 <li>
766 <em>cc</em> will avoid including anyone mentioned in Cc lines in the patch header
767 except for self (use <em>self</em> for that).
768 </p>
769 </li>
770 <li>
772 <em>bodycc</em> will avoid including anyone mentioned in Cc lines in the
773 patch body (commit message) except for self (use <em>self</em> for that).
774 </p>
775 </li>
776 <li>
778 <em>sob</em> will avoid including anyone mentioned in Signed-off-by lines except
779 for self (use <em>self</em> for that).
780 </p>
781 </li>
782 <li>
784 <em>cccmd</em> will avoid running the --cc-cmd.
785 </p>
786 </li>
787 <li>
789 <em>body</em> is equivalent to <em>sob</em> + <em>bodycc</em>
790 </p>
791 </li>
792 <li>
794 <em>all</em> will suppress all auto cc values.
795 </p>
796 </li>
797 </ul></div>
798 <div class="paragraph"><p>Default is the value of <em>sendemail.suppresscc</em> configuration value; if
799 that is unspecified, default to <em>self</em> if --suppress-from is
800 specified, as well as <em>body</em> if --no-signed-off-cc is specified.</p></div>
801 </dd>
802 <dt class="hdlist1">
803 --[no-]suppress-from
804 </dt>
805 <dd>
807 If this is set, do not add the From: address to the cc: list.
808 Default is the value of <em>sendemail.suppressfrom</em> configuration
809 value; if that is unspecified, default to --no-suppress-from.
810 </p>
811 </dd>
812 <dt class="hdlist1">
813 --[no-]thread
814 </dt>
815 <dd>
817 If this is set, the In-Reply-To and References headers will be
818 added to each email sent. Whether each mail refers to the
819 previous email (<tt>deep</tt> threading per <em>git format-patch</em>
820 wording) or to the first email (<tt>shallow</tt> threading) is
821 governed by "--[no-]chain-reply-to".
822 </p>
823 <div class="paragraph"><p>If disabled with "--no-thread", those headers will not be added
824 (unless specified with --in-reply-to). Default is the value of the
825 <em>sendemail.thread</em> configuration value; if that is unspecified,
826 default to --thread.</p></div>
827 <div class="paragraph"><p>It is up to the user to ensure that no In-Reply-To header already
828 exists when <em>git send-email</em> is asked to add it (especially note that
829 <em>git format-patch</em> can be configured to do the threading itself).
830 Failure to do so may not produce the expected result in the
831 recipient&#8217;s MUA.</p></div>
832 </dd>
833 </dl></div>
834 <h3 id="_administering">Administering</h3><div style="clear:left"></div>
835 <div class="dlist"><dl>
836 <dt class="hdlist1">
837 --confirm=&lt;mode&gt;
838 </dt>
839 <dd>
841 Confirm just before sending:
842 </p>
843 <div class="ulist"><ul>
844 <li>
846 <em>always</em> will always confirm before sending
847 </p>
848 </li>
849 <li>
851 <em>never</em> will never confirm before sending
852 </p>
853 </li>
854 <li>
856 <em>cc</em> will confirm before sending when send-email has automatically
857 added addresses from the patch to the Cc list
858 </p>
859 </li>
860 <li>
862 <em>compose</em> will confirm before sending the first message when using --compose.
863 </p>
864 </li>
865 <li>
867 <em>auto</em> is equivalent to <em>cc</em> + <em>compose</em>
868 </p>
869 </li>
870 </ul></div>
871 <div class="paragraph"><p>Default is the value of <em>sendemail.confirm</em> configuration value; if that
872 is unspecified, default to <em>auto</em> unless any of the suppress options
873 have been specified, in which case default to <em>compose</em>.</p></div>
874 </dd>
875 <dt class="hdlist1">
876 --dry-run
877 </dt>
878 <dd>
880 Do everything except actually send the emails.
881 </p>
882 </dd>
883 <dt class="hdlist1">
884 --[no-]format-patch
885 </dt>
886 <dd>
888 When an argument may be understood either as a reference or as a file name,
889 choose to understand it as a format-patch argument (<em>--format-patch</em>)
890 or as a file name (<em>--no-format-patch</em>). By default, when such a conflict
891 occurs, git send-email will fail.
892 </p>
893 </dd>
894 <dt class="hdlist1">
895 --quiet
896 </dt>
897 <dd>
899 Make git-send-email less verbose. One line per email should be
900 all that is output.
901 </p>
902 </dd>
903 <dt class="hdlist1">
904 --[no-]validate
905 </dt>
906 <dd>
908 Perform sanity checks on patches.
909 Currently, validation means the following:
910 </p>
911 <div class="ulist"><ul>
912 <li>
914 Warn of patches that contain lines longer than 998 characters; this
915 is due to SMTP limits as described by <a href="http://www.ietf.org/rfc/rfc2821.txt">http://www.ietf.org/rfc/rfc2821.txt</a>.
916 </p>
917 </li>
918 </ul></div>
919 <div class="paragraph"><p>Default is the value of <em>sendemail.validate</em>; if this is not set,
920 default to <em>--validate</em>.</p></div>
921 </dd>
922 <dt class="hdlist1">
923 --force
924 </dt>
925 <dd>
927 Send emails even if safety checks would prevent it.
928 </p>
929 </dd>
930 </dl></div>
931 </div>
932 <h2 id="_configuration">CONFIGURATION</h2>
933 <div class="sectionbody">
934 <div class="dlist"><dl>
935 <dt class="hdlist1">
936 sendemail.aliasesfile
937 </dt>
938 <dd>
940 To avoid typing long email addresses, point this to one or more
941 email aliases files. You must also supply <em>sendemail.aliasfiletype</em>.
942 </p>
943 </dd>
944 <dt class="hdlist1">
945 sendemail.aliasfiletype
946 </dt>
947 <dd>
949 Format of the file(s) specified in sendemail.aliasesfile. Must be
950 one of <em>mutt</em>, <em>mailrc</em>, <em>pine</em>, <em>elm</em>, or <em>gnus</em>.
951 </p>
952 </dd>
953 <dt class="hdlist1">
954 sendemail.multiedit
955 </dt>
956 <dd>
958 If true (default), a single editor instance will be spawned to edit
959 files you have to edit (patches when <em>--annotate</em> is used, and the
960 summary when <em>--compose</em> is used). If false, files will be edited one
961 after the other, spawning a new editor each time.
962 </p>
963 </dd>
964 <dt class="hdlist1">
965 sendemail.confirm
966 </dt>
967 <dd>
969 Sets the default for whether to confirm before sending. Must be
970 one of <em>always</em>, <em>never</em>, <em>cc</em>, <em>compose</em>, or <em>auto</em>. See <em>--confirm</em>
971 in the previous section for the meaning of these values.
972 </p>
973 </dd>
974 </dl></div>
975 </div>
976 <h2 id="_example">EXAMPLE</h2>
977 <div class="sectionbody">
978 <h3 id="_use_gmail_as_the_smtp_server">Use gmail as the smtp server</h3><div style="clear:left"></div>
979 <div class="paragraph"><p>To use <em>git send-email</em> to send your patches through the GMail SMTP server,
980 edit ~/.gitconfig to specify your account settings:</p></div>
981 <div class="literalblock">
982 <div class="content">
983 <pre><tt>[sendemail]
984 smtpencryption = tls
985 smtpserver = smtp.gmail.com
986 smtpuser = yourname@gmail.com
987 smtpserverport = 587</tt></pre>
988 </div></div>
989 <div class="paragraph"><p>Once your commits are ready to be sent to the mailing list, run the
990 following commands:</p></div>
991 <div class="literalblock">
992 <div class="content">
993 <pre><tt>$ git format-patch --cover-letter -M origin/master -o outgoing/
994 $ edit outgoing/0000-*
995 $ git send-email outgoing/*</tt></pre>
996 </div></div>
997 <div class="paragraph"><p>Note: the following perl modules are required
998 Net::SMTP::SSL, MIME::Base64 and Authen::SASL</p></div>
999 </div>
1000 <h2 id="_see_also">SEE ALSO</h2>
1001 <div class="sectionbody">
1002 <div class="paragraph"><p><a href="git-format-patch.html">git-format-patch(1)</a>, <a href="git-imap-send.html">git-imap-send(1)</a>, mbox(5)</p></div>
1003 </div>
1004 <h2 id="_git">GIT</h2>
1005 <div class="sectionbody">
1006 <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
1007 </div>
1008 <div id="footer">
1009 <div id="footer-text">
1010 Last updated 2011-05-05 01:29:54 UTC
1011 </div>
1012 </div>
1013 </body>
1014 </html>