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.2.5" />
   7 <style type="text/css">
   8 /* Debug borders */
   9 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
  10 /*
  11   border: 1px solid red;
  12 */
  13 }
  14
  15 body {
  16   margin: 1em 5% 1em 5%;
  17 }
  18
  19 a {
  20   color: blue;
  21   text-decoration: underline;
  22 }
  23 a:visited {
  24   color: fuchsia;
  25 }
  26
  27 em {
  28   font-style: italic;
  29 }
  30
  31 strong {
  32   font-weight: bold;
  33 }
  34
  35 tt {
  36   color: navy;
  37 }
  38
  39 h1, h2, h3, h4, h5, h6 {
  40   color: #527bbd;
  41   font-family: sans-serif;
  42   margin-top: 1.2em;
  43   margin-bottom: 0.5em;
  44   line-height: 1.3;
  45 }
  46
  47 h1, h2, h3 {
  48   border-bottom: 2px solid silver;
  49 }
  50 h2 {
  51   padding-top: 0.5em;
  52 }
  53 h3 {
  54   float: left;
  55 }
  56 h3 + * {
  57   clear: left;
  58 }
  59
  60 div.sectionbody {
  61   font-family: serif;
  62   margin-left: 0;
  63 }
  64
  65 hr {
  66   border: 1px solid silver;
  67 }
  68
  69 p {
  70   margin-top: 0.5em;
  71   margin-bottom: 0.5em;
  72 }
  73
  74 pre {
  75   padding: 0;
  76   margin: 0;
  77 }
  78
  79 span#author {
  80   color: #527bbd;
  81   font-family: sans-serif;
  82   font-weight: bold;
  83   font-size: 1.1em;
  84 }
  85 span#email {
  86 }
  87 span#revision {
  88   font-family: sans-serif;
  89 }
  90
  91 div#footer {
  92   font-family: sans-serif;
  93   font-size: small;
  94   border-top: 2px solid silver;
  95   padding-top: 0.5em;
  96   margin-top: 4.0em;
  97 }
  98 div#footer-text {
  99   float: left;
 100   padding-bottom: 0.5em;
 101 }
 102 div#footer-badges {
 103   float: right;
 104   padding-bottom: 0.5em;
 105 }
 106
 107 div#preamble,
 108 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
 109 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 110 div.admonitionblock {
 111   margin-right: 10%;
 112   margin-top: 1.5em;
 113   margin-bottom: 1.5em;
 114 }
 115 div.admonitionblock {
 116   margin-top: 2.5em;
 117   margin-bottom: 2.5em;
 118 }
 119
 120 div.content { /* Block element content. */
 121   padding: 0;
 122 }
 123
 124 /* Block element titles. */
 125 div.title, caption.title {
 126   font-family: sans-serif;
 127   font-weight: bold;
 128   text-align: left;
 129   margin-top: 1.0em;
 130   margin-bottom: 0.5em;
 131 }
 132 div.title + * {
 133   margin-top: 0;
 134 }
 135
 136 td div.title:first-child {
 137   margin-top: 0.0em;
 138 }
 139 div.content div.title:first-child {
 140   margin-top: 0.0em;
 141 }
 142 div.content + div.title {
 143   margin-top: 0.0em;
 144 }
 145
 146 div.sidebarblock > div.content {
 147   background: #ffffee;
 148   border: 1px solid silver;
 149   padding: 0.5em;
 150 }
 151
 152 div.listingblock {
 153   margin-right: 0%;
 154 }
 155 div.listingblock > div.content {
 156   border: 1px solid silver;
 157   background: #f4f4f4;
 158   padding: 0.5em;
 159 }
 160
 161 div.quoteblock > div.content {
 162   padding-left: 2.0em;
 163 }
 164
 165 div.attribution {
 166   text-align: right;
 167 }
 168 div.verseblock + div.attribution {
 169   text-align: left;
 170 }
 171
 172 div.admonitionblock .icon {
 173   vertical-align: top;
 174   font-size: 1.1em;
 175   font-weight: bold;
 176   text-decoration: underline;
 177   color: #527bbd;
 178   padding-right: 0.5em;
 179 }
 180 div.admonitionblock td.content {
 181   padding-left: 0.5em;
 182   border-left: 2px solid silver;
 183 }
 184
 185 div.exampleblock > div.content {
 186   border-left: 2px solid silver;
 187   padding: 0.5em;
 188 }
 189
 190 div.verseblock div.content {
 191   white-space: pre;
 192 }
 193
 194 div.imageblock div.content { padding-left: 0; }
 195 div.imageblock img { border: 1px solid silver; }
 196 span.image img { border-style: none; }
 197
 198 dl {
 199   margin-top: 0.8em;
 200   margin-bottom: 0.8em;
 201 }
 202 dt {
 203   margin-top: 0.5em;
 204   margin-bottom: 0;
 205   font-style: italic;
 206 }
 207 dd > *:first-child {
 208   margin-top: 0;
 209 }
 210
 211 ul, ol {
 212     list-style-position: outside;
 213 }
 214 div.olist2 ol {
 215   list-style-type: lower-alpha;
 216 }
 217
 218 div.tableblock > table {
 219   border: 3px solid #527bbd;
 220 }
 221 thead {
 222   font-family: sans-serif;
 223   font-weight: bold;
 224 }
 225 tfoot {
 226   font-weight: bold;
 227 }
 228
 229 div.hlist {
 230   margin-top: 0.8em;
 231   margin-bottom: 0.8em;
 232 }
 233 div.hlist td {
 234   padding-bottom: 5px;
 235 }
 236 td.hlist1 {
 237   vertical-align: top;
 238   font-style: italic;
 239   padding-right: 0.8em;
 240 }
 241 td.hlist2 {
 242   vertical-align: top;
 243 }
 244
 245 @media print {
 246   div#footer-badges { display: none; }
 247 }
 248
 249 div#toctitle {
 250   color: #527bbd;
 251   font-family: sans-serif;
 252   font-size: 1.1em;
 253   font-weight: bold;
 254   margin-top: 1.0em;
 255   margin-bottom: 0.1em;
 256 }
 257
 258 div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
 259   margin-top: 0;
 260   margin-bottom: 0;
 261 }
 262 div.toclevel2 {
 263   margin-left: 2em;
 264   font-size: 0.9em;
 265 }
 266 div.toclevel3 {
 267   margin-left: 4em;
 268   font-size: 0.9em;
 269 }
 270 div.toclevel4 {
 271   margin-left: 6em;
 272   font-size: 0.9em;
 273 }
 274 include1::./stylesheets/xhtml11-manpage.css[]
 275 /* Workarounds for IE6's broken and incomplete CSS2. */
 276
 277 div.sidebar-content {
 278   background: #ffffee;
 279   border: 1px solid silver;
 280   padding: 0.5em;
 281 }
 282 div.sidebar-title, div.image-title {
 283   font-family: sans-serif;
 284   font-weight: bold;
 285   margin-top: 0.0em;
 286   margin-bottom: 0.5em;
 287 }
 288
 289 div.listingblock div.content {
 290   border: 1px solid silver;
 291   background: #f4f4f4;
 292   padding: 0.5em;
 293 }
 294
 295 div.quoteblock-content {
 296   padding-left: 2.0em;
 297 }
 298
 299 div.exampleblock-content {
 300   border-left: 2px solid silver;
 301   padding-left: 0.5em;
 302 }
 303
 304 /* IE6 sets dynamically generated links as visited. */
 305 div#toc a:visited { color: blue; }
 306 </style>
 307 <title>git-send-email(1)</title>
 308 </head>
 309 <body>
 310 <div id="header">
 311 <h1>
 312 git-send-email(1) Manual Page
 313 </h1>
 314 <h2>NAME</h2>
 315 <div class="sectionbody">
 316 <p>git-send-email -
 317    Send a collection of patches as emails
 318 </p>
 319 </div>
 320 </div>
 321 <h2>SYNOPSIS</h2>
 322 <div class="sectionbody">
 323 <div class="para"><p><em>git send-email</em> [options] &lt;file|directory|rev-list options&gt;&#8230;</p></div>
 324 </div>
 325 <h2 id="_description">DESCRIPTION</h2>
 326 <div class="sectionbody">
 327 <div class="para"><p>Takes the patches given on the command line and emails them out.
 328 Patches can be specified as files, directories (which will send all
 329 files in the directory), or directly as a revision list.  In the
 330 last case, any format accepted by <a href="git-format-patch.html">git-format-patch(1)</a> can
 331 be passed to git send-email.</p></div>
 332 <div class="para"><p>The header of the email is configurable by command line options.  If not
 333 specified on the command line, the user will be prompted with a ReadLine
 334 enabled interface to provide the necessary information.</p></div>
 335 <div class="para"><p>There are two formats accepted for patch files:</p></div>
 336 <div class="olist"><ol>
 337 <li>
 338 <p>
 339 mbox format files
 340 </p>
 341 <div class="para"><p>This is what <a href="git-format-patch.html">git-format-patch(1)</a> generates.  Most headers and MIME
 342 formatting are ignored.</p></div>
 343 </li>
 344 <li>
 345 <p>
 346 The original format used by Greg Kroah-Hartman's <em>send_lots_of_email.pl</em>
 347 script
 348 </p>
 349 <div class="para"><p>This format expects the first line of the file to contain the "Cc:" value
 350 and the "Subject:" of the message as the second line.</p></div>
 351 </li>
 352 </ol></div>
 353 </div>
 354 <h2 id="_options">OPTIONS</h2>
 355 <div class="sectionbody">
 356 <h3 id="_composing">Composing</h3><div style="clear:left"></div>
 357 <div class="vlist"><dl>
 358 <dt>
 359 --annotate
 360 </dt>
 361 <dd>
 362 <p>
 363         Review and edit each patch you're about to send. See the
 364         CONFIGURATION section for <em>sendemail.multiedit</em>.
 365 </p>
 366 </dd>
 367 <dt>
 368 --bcc=&lt;address&gt;
 369 </dt>
 370 <dd>
 371 <p>
 372         Specify a "Bcc:" value for each email. Default is the value of
 373         <em>sendemail.bcc</em>.
 374 </p>
 375 <div class="para"><p>The --bcc option must be repeated for each user you want on the bcc list.</p></div>
 376 </dd>
 377 <dt>
 378 --cc=&lt;address&gt;
 379 </dt>
 380 <dd>
 381 <p>
 382         Specify a starting "Cc:" value for each email.
 383         Default is the value of <em>sendemail.cc</em>.
 384 </p>
 385 <div class="para"><p>The --cc option must be repeated for each user you want on the cc list.</p></div>
 386 </dd>
 387 <dt>
 388 --compose
 389 </dt>
 390 <dd>
 391 <p>
 392         Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
 393         introductory message for the patch series.
 394 </p>
 395 <div class="para"><p>When <em>--compose</em> is used, git send-email will use the From, Subject, and
 396 In-Reply-To headers specified in the message. If the body of the message
 397 (what you type after the headers and a blank line) only contains blank
 398 (or GIT: prefixed) lines the summary won't be sent, but From, Subject,
 399 and In-Reply-To headers will be used unless they are removed.</p></div>
 400 <div class="para"><p>Missing From or In-Reply-To headers will be prompted for.</p></div>
 401 <div class="para"><p>See the CONFIGURATION section for <em>sendemail.multiedit</em>.</p></div>
 402 </dd>
 403 <dt>
 404 --from=&lt;address&gt;
 405 </dt>
 406 <dd>
 407 <p>
 408         Specify the sender of the emails.  If not specified on the command line,
 409         the value of the <em>sendemail.from</em> configuration option is used.  If
 410         neither the command line option nor <em>sendemail.from</em> are set, then the
 411         user will be prompted for the value.  The default for the prompt will be
 412         the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not
 413         set, as returned by "git var -l".
 414 </p>
 415 </dd>
 416 <dt>
 417 --in-reply-to=&lt;identifier&gt;
 418 </dt>
 419 <dd>
 420 <p>
 421         Specify the contents of the first In-Reply-To header.
 422         Subsequent emails will refer to the previous email
 423         instead of this if --chain-reply-to is set (the default)
 424         Only necessary if --compose is also set.  If --compose
 425         is not set, this will be prompted for.
 426 </p>
 427 </dd>
 428 <dt>
 429 --subject=&lt;string&gt;
 430 </dt>
 431 <dd>
 432 <p>
 433         Specify the initial subject of the email thread.
 434         Only necessary if --compose is also set.  If --compose
 435         is not set, this will be prompted for.
 436 </p>
 437 </dd>
 438 <dt>
 439 --to=&lt;address&gt;
 440 </dt>
 441 <dd>
 442 <p>
 443         Specify the primary recipient of the emails generated. Generally, this
 444         will be the upstream maintainer of the project involved. Default is the
 445         value of the <em>sendemail.to</em> configuration value; if that is unspecified,
 446         this will be prompted for.
 447 </p>
 448 <div class="para"><p>The --to option must be repeated for each user you want on the to list.</p></div>
 449 </dd>
 450 </dl></div>
 451 <h3 id="_sending">Sending</h3><div style="clear:left"></div>
 452 <div class="vlist"><dl>
 453 <dt>
 454 --envelope-sender=&lt;address&gt;
 455 </dt>
 456 <dd>
 457 <p>
 458         Specify the envelope sender used to send the emails.
 459         This is useful if your default address is not the address that is
 460         subscribed to a list. If you use the sendmail binary, you must have
 461         suitable privileges for the -f parameter. Default is the value of
 462         the <em>sendemail.envelopesender</em> configuration variable; if that is
 463         unspecified, choosing the envelope sender is left to your MTA.
 464 </p>
 465 </dd>
 466 <dt>
 467 --smtp-encryption=&lt;encryption&gt;
 468 </dt>
 469 <dd>
 470 <p>
 471         Specify the encryption to use, either <em>ssl</em> or <em>tls</em>.  Any other
 472         value reverts to plain SMTP.  Default is the value of
 473         <em>sendemail.smtpencryption</em>.
 474 </p>
 475 </dd>
 476 <dt>
 477 --smtp-pass[=&lt;password&gt;]
 478 </dt>
 479 <dd>
 480 <p>
 481         Password for SMTP-AUTH. The argument is optional: If no
 482         argument is specified, then the empty string is used as
 483         the password. Default is the value of <em>sendemail.smtppass</em>,
 484         however <em>--smtp-pass</em> always overrides this value.
 485 </p>
 486 <div class="para"><p>Furthermore, passwords need not be specified in configuration files
 487 or on the command line. If a username has been specified (with
 488 <em>--smtp-user</em> or a <em>sendemail.smtpuser</em>), but no password has been
 489 specified (with <em>--smtp-pass</em> or <em>sendemail.smtppass</em>), then the
 490 user is prompted for a password while the input is masked for privacy.</p></div>
 491 </dd>
 492 <dt>
 493 --smtp-server=&lt;host&gt;
 494 </dt>
 495 <dd>
 496 <p>
 497         If set, specifies the outgoing SMTP server to use (e.g.
 498         <tt>smtp.example.com</tt> or a raw IP address).  Alternatively it can
 499         specify a full pathname of a sendmail-like program instead;
 500         the program must support the <tt>-i</tt> option.  Default value can
 501         be specified by the <em>sendemail.smtpserver</em> configuration
 502         option; the built-in default is <tt>/usr/sbin/sendmail</tt> or
 503         <tt>/usr/lib/sendmail</tt> if such program is available, or
 504         <tt>localhost</tt> otherwise.
 505 </p>
 506 </dd>
 507 <dt>
 508 --smtp-server-port=&lt;port&gt;
 509 </dt>
 510 <dd>
 511 <p>
 512         Specifies a port different from the default port (SMTP
 513         servers typically listen to smtp port 25, but may also listen to
 514         submission port 587, or the common SSL smtp port 465);
 515         symbolic port names (e.g. "submission" instead of 587)
 516         are also accepted. The port can also be set with the
 517         <em>sendemail.smtpserverport</em> configuration variable.
 518 </p>
 519 </dd>
 520 <dt>
 521 --smtp-ssl
 522 </dt>
 523 <dd>
 524 <p>
 525         Legacy alias for <em>--smtp-encryption ssl</em>.
 526 </p>
 527 </dd>
 528 <dt>
 529 --smtp-user=&lt;user&gt;
 530 </dt>
 531 <dd>
 532 <p>
 533         Username for SMTP-AUTH. Default is the value of <em>sendemail.smtpuser</em>;
 534         if a username is not specified (with <em>--smtp-user</em> or <em>sendemail.smtpuser</em>),
 535         then authentication is not attempted.
 536 </p>
 537 </dd>
 538 </dl></div>
 539 <h3 id="_automating">Automating</h3><div style="clear:left"></div>
 540 <div class="vlist"><dl>
 541 <dt>
 542 --cc-cmd=&lt;command&gt;
 543 </dt>
 544 <dd>
 545 <p>
 546         Specify a command to execute once per patch file which
 547         should generate patch file specific "Cc:" entries.
 548         Output of this command must be single email address per line.
 549         Default is the value of <em>sendemail.cccmd</em> configuration value.
 550 </p>
 551 </dd>
 552 <dt>
 553 --[no-]chain-reply-to
 554 </dt>
 555 <dd>
 556 <p>
 557         If this is set, each email will be sent as a reply to the previous
 558         email sent.  If disabled with "--no-chain-reply-to", all emails after
 559         the first will be sent as replies to the first email sent.  When using
 560         this, it is recommended that the first file given be an overview of the
 561         entire patch series. Default is the value of the <em>sendemail.chainreplyto</em>
 562         configuration value; if that is unspecified, default to --chain-reply-to.
 563 </p>
 564 </dd>
 565 <dt>
 566 --identity=&lt;identity&gt;
 567 </dt>
 568 <dd>
 569 <p>
 570         A configuration identity. When given, causes values in the
 571         <em>sendemail.&lt;identity&gt;</em> subsection to take precedence over
 572         values in the <em>sendemail</em> section. The default identity is
 573         the value of <em>sendemail.identity</em>.
 574 </p>
 575 </dd>
 576 <dt>
 577 --[no-]signed-off-by-cc
 578 </dt>
 579 <dd>
 580 <p>
 581         If this is set, add emails found in Signed-off-by: or Cc: lines to the
 582         cc list. Default is the value of <em>sendemail.signedoffbycc</em> configuration
 583         value; if that is unspecified, default to --signed-off-by-cc.
 584 </p>
 585 </dd>
 586 <dt>
 587 --suppress-cc=&lt;category&gt;
 588 </dt>
 589 <dd>
 590 <p>
 591         Specify an additional category of recipients to suppress the
 592         auto-cc of:
 593 </p>
 594 <div class="ilist"><ul>
 595 <li>
 596 <p>
 597 <em>author</em> will avoid including the patch author
 598 </p>
 599 </li>
 600 <li>
 601 <p>
 602 <em>self</em> will avoid including the sender
 603 </p>
 604 </li>
 605 <li>
 606 <p>
 607 <em>cc</em> will avoid including anyone mentioned in Cc lines in the patch header
 608   except for self (use <em>self</em> for that).
 609 </p>
 610 </li>
 611 <li>
 612 <p>
 613 <em>bodycc</em> will avoid including anyone mentioned in Cc lines in the
 614   patch body (commit message) except for self (use <em>self</em> for that).
 615 </p>
 616 </li>
 617 <li>
 618 <p>
 619 <em>sob</em> will avoid including anyone mentioned in Signed-off-by lines except
 620    for self (use <em>self</em> for that).
 621 </p>
 622 </li>
 623 <li>
 624 <p>
 625 <em>cccmd</em> will avoid running the --cc-cmd.
 626 </p>
 627 </li>
 628 <li>
 629 <p>
 630 <em>body</em> is equivalent to <em>sob</em> + <em>bodycc</em>
 631 </p>
 632 </li>
 633 <li>
 634 <p>
 635 <em>all</em> will suppress all auto cc values.
 636 </p>
 637 </li>
 638 </ul></div>
 639 <div class="para"><p>Default is the value of <em>sendemail.suppresscc</em> configuration value; if
 640 that is unspecified, default to <em>self</em> if --suppress-from is
 641 specified, as well as <em>body</em> if --no-signed-off-cc is specified.</p></div>
 642 </dd>
 643 <dt>
 644 --[no-]suppress-from
 645 </dt>
 646 <dd>
 647 <p>
 648         If this is set, do not add the From: address to the cc: list.
 649         Default is the value of <em>sendemail.suppressfrom</em> configuration
 650         value; if that is unspecified, default to --no-suppress-from.
 651 </p>
 652 </dd>
 653 <dt>
 654 --[no-]thread
 655 </dt>
 656 <dd>
 657 <p>
 658         If this is set, the In-Reply-To and References headers will be
 659         added to each email sent.  Whether each mail refers to the
 660         previous email (<tt>deep</tt> threading per <em>git format-patch</em>
 661         wording) or to the first email (<tt>shallow</tt> threading) is
 662         governed by "--[no-]chain-reply-to".
 663 </p>
 664 <div class="para"><p>If disabled with "--no-thread", those headers will not be added
 665 (unless specified with --in-reply-to).  Default is the value of the
 666 <em>sendemail.thread</em> configuration value; if that is unspecified,
 667 default to --thread.</p></div>
 668 <div class="para"><p>It is up to the user to ensure that no In-Reply-To header already
 669 exists when <em>git send-email</em> is asked to add it (especially note that
 670 <em>git format-patch</em> can be configured to do the threading itself).
 671 Failure to do so may not produce the expected result in the
 672 recipient's MUA.</p></div>
 673 </dd>
 674 </dl></div>
 675 <h3 id="_administering">Administering</h3><div style="clear:left"></div>
 676 <div class="vlist"><dl>
 677 <dt>
 678 --confirm=&lt;mode&gt;
 679 </dt>
 680 <dd>
 681 <p>
 682         Confirm just before sending:
 683 </p>
 684 <div class="ilist"><ul>
 685 <li>
 686 <p>
 687 <em>always</em> will always confirm before sending
 688 </p>
 689 </li>
 690 <li>
 691 <p>
 692 <em>never</em> will never confirm before sending
 693 </p>
 694 </li>
 695 <li>
 696 <p>
 697 <em>cc</em> will confirm before sending when send-email has automatically
 698   added addresses from the patch to the Cc list
 699 </p>
 700 </li>
 701 <li>
 702 <p>
 703 <em>compose</em> will confirm before sending the first message when using --compose.
 704 </p>
 705 </li>
 706 <li>
 707 <p>
 708 <em>auto</em> is equivalent to <em>cc</em> + <em>compose</em>
 709 </p>
 710 </li>
 711 </ul></div>
 712 <div class="para"><p>Default is the value of <em>sendemail.confirm</em> configuration value; if that
 713 is unspecified, default to <em>auto</em> unless any of the suppress options
 714 have been specified, in which case default to <em>compose</em>.</p></div>
 715 </dd>
 716 <dt>
 717 --dry-run
 718 </dt>
 719 <dd>
 720 <p>
 721         Do everything except actually send the emails.
 722 </p>
 723 </dd>
 724 <dt>
 725 --[no-]format-patch
 726 </dt>
 727 <dd>
 728 <p>
 729         When an argument may be understood either as a reference or as a file name,
 730         choose to understand it as a format-patch argument (<em>--format-patch</em>)
 731         or as a file name (<em>--no-format-patch</em>). By default, when such a conflict
 732         occurs, git send-email will fail.
 733 </p>
 734 </dd>
 735 <dt>
 736 --quiet
 737 </dt>
 738 <dd>
 739 <p>
 740         Make git-send-email less verbose.  One line per email should be
 741         all that is output.
 742 </p>
 743 </dd>
 744 <dt>
 745 --[no-]validate
 746 </dt>
 747 <dd>
 748 <p>
 749         Perform sanity checks on patches.
 750         Currently, validation means the following:
 751 </p>
 752 <div class="ilist"><ul>
 753 <li>
 754 <p>
 755 Warn of patches that contain lines longer than 998 characters; this
 756                         is due to SMTP limits as described by http://www.ietf.org/rfc/rfc2821.txt.
 757 </p>
 758 </li>
 759 </ul></div>
 760 <div class="para"><p>Default is the value of <em>sendemail.validate</em>; if this is not set,
 761 default to <em>--validate</em>.</p></div>
 762 </dd>
 763 </dl></div>
 764 </div>
 765 <h2 id="_configuration">CONFIGURATION</h2>
 766 <div class="sectionbody">
 767 <div class="vlist"><dl>
 768 <dt>
 769 sendemail.aliasesfile
 770 </dt>
 771 <dd>
 772 <p>
 773         To avoid typing long email addresses, point this to one or more
 774         email aliases files.  You must also supply <em>sendemail.aliasfiletype</em>.
 775 </p>
 776 </dd>
 777 <dt>
 778 sendemail.aliasfiletype
 779 </dt>
 780 <dd>
 781 <p>
 782         Format of the file(s) specified in sendemail.aliasesfile. Must be
 783         one of <em>mutt</em>, <em>mailrc</em>, <em>pine</em>, <em>elm</em>, or <em>gnus</em>.
 784 </p>
 785 </dd>
 786 <dt>
 787 sendemail.multiedit
 788 </dt>
 789 <dd>
 790 <p>
 791         If true (default), a single editor instance will be spawned to edit
 792         files you have to edit (patches when <em>--annotate</em> is used, and the
 793         summary when <em>--compose</em> is used). If false, files will be edited one
 794         after the other, spawning a new editor each time.
 795 </p>
 796 </dd>
 797 <dt>
 798 sendemail.confirm
 799 </dt>
 800 <dd>
 801 <p>
 802         Sets the default for whether to confirm before sending. Must be
 803         one of <em>always</em>, <em>never</em>, <em>cc</em>, <em>compose</em>, or <em>auto</em>. See <em>--confirm</em>
 804         in the previous section for the meaning of these values.
 805 </p>
 806 </dd>
 807 </dl></div>
 808 </div>
 809 <h2 id="_author">Author</h2>
 810 <div class="sectionbody">
 811 <div class="para"><p>Written by Ryan Anderson &lt;ryan@michonline.com&gt;</p></div>
 812 <div class="para"><p>git-send-email is originally based upon
 813 send_lots_of_email.pl by Greg Kroah-Hartman.</p></div>
 814 </div>
 815 <h2 id="_documentation">Documentation</h2>
 816 <div class="sectionbody">
 817 <div class="para"><p>Documentation by Ryan Anderson</p></div>
 818 </div>
 819 <h2 id="_git">GIT</h2>
 820 <div class="sectionbody">
 821 <div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
 822 </div>
 823 <div id="footer">
 824 <div id="footer-text">
 825 Last updated 2009-08-03 08:06:58 UTC
 826 </div>
 827 </div>
 828 </body>
 829 </html>