git-send-email.html

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