From: Junio C Hamano <gitster@pobox.com>
To: David Brown <git@davidb.org>
Cc: git@vger.kernel.org, Joel Becker <Joel.Becker@oracle.com>
Subject: Re: [PATCH] git-send-email: Generalize auto-cc recipient mechanism.
Date: Tue, 25 Dec 2007 13:04:54 -0800 [thread overview]
Message-ID: <7vk5n2o58p.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1198532163-25308-1-git-send-email-git@davidb.org> (David Brown's message of "Mon, 24 Dec 2007 13:36:03 -0800")
David Brown <git@davidb.org> writes:
> ...
> self - patch sender. Same as --suppress-from.
> author - patch author.
> cc - cc lines mentioned in the patch.
> cccmd - avoid running the cccmd.
> sob - signed off by lines.
> all - all non-explicit recipients
>
> Signed-off-by: David Brown <git@davidb.org>
> ...
> What bothers me most about this change is that --signed-of-cc
> and --suppress-from are silently ignored if --suppress-cc is given, either
> on the command line, or in the config.
The order in which various variables are set in the current code
before your patch is like this:
* my ($var) introduces them -- they are undefined at the
beginning;
* GetOptions() may set them to explicit values;
* read_config(), first for the specific sendemail identity and
then for the generic ones, fill the ones that are still
undefined;
* the built-in default from %config_bool_settings are used to
fill the ones that are still undefined at this point;
Now, I think you can build on top of the above by adding the
following after that sequence:
* fill %suppress_cc with explicit @suppress_cc GetOptions and
read_config() read;
* if the --suppress-from and/or --signed-off-by-cc, either from
GetOptions() or from read_config() are given, make them
override what @suppress_cc says. So giving --suppress-cc=all
and --signed-off-by-cc at the same time will still send cc to
people who signed off the patch (because these old-style ones
are more specific).
Perhaps something like this (untested, of course!) patch on top
of yours.
git-send-email.perl | 16 +++++++++-------
1 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/git-send-email.perl b/git-send-email.perl
index 1f03d12..cde5ffb 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -188,8 +188,8 @@ my (@suppress_cc);
my %config_bool_settings = (
"thread" => [\$thread, 1],
"chainreplyto" => [\$chain_reply_to, 1],
- "suppressfrom" => [\$suppress_from, 0],
- "signedoffcc" => [\$signed_off_cc, 1],
+ "suppressfrom" => [\$suppress_from, undef],
+ "signedoffcc" => [\$signed_off_cc, undef],
"smtpssl" => [\$smtp_ssl, 0],
);
@@ -279,18 +279,20 @@ if (@suppress_cc) {
unless $entry =~ /^(all|cccmd|cc|author|self|sob)$/;
$suppress_cc{$entry} = 1;
}
-} else {
- # Convert the old-style options.
- $suppress_cc{'self'} = 1 if $suppress_from;
- $suppress_cc{'sob'} = 1 unless $signed_off_cc;
}
-
if ($suppress_cc{'all'}) {
foreach my $entry (qw (ccmd cc author self sob)) {
$suppress_cc{$entry} = 1;
}
delete $suppress_cc{'all'};
}
+# If explicit old-style ones are specified, they trump supress-cc
+if (defined $suppress_from) {
+ $suppress_cc{'self'} = $suppress_from;
+}
+if (defined $signed_off_cc) {
+ $suppress_cc{'sob'} = !$signed_off_cc;
+}
my ($repoauthor) = $repo->ident_person('author');
my ($repocommitter) = $repo->ident_person('committer');
next prev parent reply other threads:[~2007-12-25 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 6:01 [PATCH] git-send-email: Add --suppress-all-from option David Brown
2007-12-21 11:05 ` Joel Becker
2007-12-21 11:14 ` Brian Swetland
2007-12-21 17:43 ` Junio C Hamano
2007-12-21 19:21 ` Joel Becker
2007-12-22 0:55 ` Theodore Tso
2007-12-21 22:37 ` David Brown
2007-12-24 19:01 ` [PATCH] git-send-email: Generalize auto-cc recipient mechanism David Brown
2007-12-24 21:03 ` Joel Becker
2007-12-24 21:26 ` [PATCH] git-send-email: Add --suppress-cc all David Brown
2007-12-24 21:59 ` Joel Becker
2007-12-24 21:36 ` [PATCH] git-send-email: Generalize auto-cc recipient mechanism David Brown
2007-12-25 21:04 ` Junio C Hamano [this message]
2007-12-26 3:39 ` David Brown
2007-12-26 3:56 ` David Brown
2007-12-26 4:54 ` Sean
2007-12-26 5:32 ` David Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vk5n2o58p.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Joel.Becker@oracle.com \
--cc=git@davidb.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).