1GIT-SEND-EMAIL(1) Git Manual GIT-SEND-EMAIL(1)
2
6 git-send-email - Send a collection of patches as emails
7
9 git-send-email [options] <file|directory> [... file|directory]
10
12 Takes the patches given on the command line and emails them out.
13 The header of the email is configurable by command line options. If not
15 specified on the command line, the user will be prompted with a
16 ReadLine enabled interface to provide the necessary information.
17
19 The options available are:
20 --bcc
22 Specify a "Bcc:" value for each email.
23 The --bcc option must be repeated for each user you want on the bcc
25 list.
26 --cc
28 Specify a starting "Cc:" value for each email.
29 The --cc option must be repeated for each user you want on the cc
31 list.
32 --cc-cmd
34 Specify a command to execute once per patch file which should
35 generate patch file specific "Cc:" entries. Output of this command
36 must be single email address per line. Default is the value of
37 sendemail.cccmd configuration value.
38 --chain-reply-to, --no-chain-reply-to
40 If this is set, each email will be sent as a reply to the previous
41 email sent. If disabled with "--no-chain-reply-to", all emails
42 after the first will be sent as replies to the first email sent.
43 When using this, it is recommended that the first file given be an
44 overview of the entire patch series. Default is the value of the
45 sendemail.chainreplyto configuration value; if that is unspecified,
46 default to --chain-reply-to.
47 --compose
49 Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
50 introductory message for the patch series.
51 --from
53 Specify the sender of the emails. This will default to the value
54 GIT_COMMITTER_IDENT, as returned by "git-var -l". The user will
55 still be prompted to confirm this entry.
56 --in-reply-to
58 Specify the contents of the first In-Reply-To header. Subsequent
59 emails will refer to the previous email instead of this if
60 --chain-reply-to is set (the default) Only necessary if --compose
61 is also set. If --compose is not set, this will be prompted for.
62 --signed-off-by-cc, --no-signed-off-by-cc
64 If this is set, add emails found in Signed-off-by: or Cc: lines to
65 the cc list. Default is the value of sendemail.signedoffcc
66 configuration value; if that is unspecified, default to
67 --signed-off-by-cc.
68 --quiet
70 Make git-send-email less verbose. One line per email should be all
71 that is output.
72 --smtp-server
74 If set, specifies the outgoing SMTP server to use (e.g.
75 smtp.example.com or a raw IP address). Alternatively it can specify
76 a full pathname of a sendmail-like program instead; the program
77 must support the -i option. Default value can be specified by the
78 sendemail.smtpserver configuration option; the built-in default is
79 /usr/sbin/sendmail or /usr/lib/sendmail if such program is
80 available, or localhost otherwise.
81 --subject
83 Specify the initial subject of the email thread. Only necessary if
84 --compose is also set. If --compose is not set, this will be
85 prompted for.
86 --suppress-from, --no-suppress-from
88 If this is set, do not add the From: address to the cc: list, if it
89 shows up in a From: line. Default is the value of
90 sendemail.suppressfrom configuration value; if that is unspecified,
91 default to --no-suppress-from.
92 --thread, --no-thread
94 If this is set, the In-Reply-To header will be set on each email
95 sent. If disabled with "--no-thread", no emails will have the
96 In-Reply-To header set. Default is the value of the
97 sendemail.thread configuration value; if that is unspecified,
98 default to --thread.
99 --dry-run
101 Do everything except actually send the emails.
102 --envelope-sender
104 Specify the envelope sender used to send the emails. This is useful
105 if your default address is not the address that is subscribed to a
106 list. If you use the sendmail binary, you must have suitable
107 privileges for the -f parameter.
108 --to
110 Specify the primary recipient of the emails generated. Generally,
111 this will be the upstream maintainer of the project involved.
112 The --to option must be repeated for each user you want on the to
114 list.
115
117 sendemail.aliasesfile
118 To avoid typing long email addresses, point this to one or more
119 email aliases files. You must also supply sendemail.aliasfiletype.
120 sendemail.aliasfiletype
122 Format of the file(s) specified in sendemail.aliasesfile. Must be
123 one of mutt, mailrc, pine, or gnus.
124 sendemail.cccmd
126 Command to execute to generate per patch file specific "Cc:"s.
127 sendemail.bcc
129 Email address (or alias) to always bcc.
130 sendemail.chainreplyto
132 Boolean value specifying the default to the --chain_reply_to
133 parameter.
134 sendemail.smtpserver
136 Default smtp server to use.
137
139 Written by Ryan Anderson <ryan@michonline.com>
140 git-send-email is originally based upon send_lots_of_email.pl by Greg
142 Kroah-Hartman.
143
145 Documentation by Ryan Anderson
146
148 Part of the git(7) suite
149Git 1.5.3.3 10/09/2007 GIT-SEND-EMAIL(1)