git-send-email: configurable bcc and chain-reply-to
Chain-reply-to is a personal perference, and is unlikely to change from patchset to patchset. Similarly, bcc is likely to have the same values every invocation is one likes to bcc oneself. So, allow both to be set via configuration variables. Signed-off-by: Avi Kivity <avi@qumranet.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
Avi Kivity committed
Mar 11, 2007 at 19:19 UTC
4a62d3f5b237fb9fab7df778ecf62906ff892065
2 files changed
+19
-1
Documentation/git-send-email.txt
+9
-1
@@ -40,7 +40,8 @@ The --cc option must be repeated for each user you want on the cc list.
40
the first will be sent as replies to the first email sent. When using
41
this, it is recommended that the first file given be an overview of the
42
entire patch series.
43
- Default is --chain-reply-to
43
+ Default is the value of the 'sendemail.chainreplyto' configuration
44
+ value; if that is unspecified, default to --chain-reply-to.
45
46
--compose::
47
Use $EDITOR to edit an introductory message for the
@@ -101,6 +102,13 @@ sendemail.aliasfiletype::
102
Format of the file(s) specified in sendemail.aliasesfile. Must be
103
one of 'mutt', 'mailrc', 'pine', or 'gnus'.
104
105
+sendemail.bcc::
106
+ Email address (or alias) to always bcc.
107
+
108
+sendemail.chainreplyto::
109
+ Boolean value specifying the default to the '--chain_reply_to'
110
+ parameter.
111
+
112
sendemail.smtpserver::
113
Default smtp server to use.
114
git-send-email.perl
+10
@@ -149,6 +149,16 @@ if ($@) {
149
$term = new FakeTerm "$@: going non-interactive";
150
}
151
152
+my $def_chain = $repo->config_boolean('sendemail.chainreplyto');
153
+if ($def_chain and $def_chain eq 'false') {
154
+ $chain_reply_to = 0;
155
+}
156
+
157
+@bcclist = $repo->config('sendemail.bcc');
158
+if (!@bcclist or !$bcclist[0]) {
159
+ @bcclist = ();
160
+}
161
+
162
# Begin by accumulating all the variables (defined above), that we will end up
163
# needing, first, from the command line:
164