From: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
To: git@vger.kernel.org
Cc: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Subject: [PATCH] send-email: Ask for in-reply message ID even if from and to is already known
Date: Tue, 1 Jun 2010 20:08:50 +0200 [thread overview]
Message-ID: <1275415730-15360-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de> (raw)
In-Reply-To: <vpqtypmn4bm.fsf@bauges.imag.fr>
This patch removes the prompting variable so git send-email always asks
for a in-reply message ID (unless specified on command line) even when
sendemail.from and sendemail.to is set in ~/.gitconfig or .git/config
Signed-off-by: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
---
git-send-email.perl | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/git-send-email.perl b/git-send-email.perl
index 111c981..4487472 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -136,7 +136,7 @@ my $auth;
sub unique_email_list(@);
sub cleanup_compose_files();
-# Variables we fill in automatically, or via prompting:
+# Variables we fill in automatically:
my (@to,$no_to,@cc,$no_cc,@initial_cc,@bcclist,$no_bcc,@xh,
$initial_reply_to,$initial_subject,@files,
$author,$sender,$smtp_authpass,$annotate,$compose,$time);
@@ -669,19 +669,16 @@ sub ask {
return undef;
}
-my $prompting = 0;
if (!defined $sender) {
$sender = $repoauthor || $repocommitter || '';
$sender = ask("Who should the emails appear to be from? [$sender] ",
default => $sender);
print "Emails will be sent from: ", $sender, "\n";
- $prompting++;
}
if (!@to) {
my $to = ask("Who should the emails be sent to? ");
push @to, parse_address_line($to) if defined $to; # sanitized/validated later
- $prompting++;
}
sub expand_aliases {
@@ -703,7 +700,7 @@ sub expand_one_alias {
@initial_cc = expand_aliases(@initial_cc);
@bcclist = expand_aliases(@bcclist);
-if ($thread && !defined $initial_reply_to && $prompting) {
+if ($thread && !defined $initial_reply_to) {
$initial_reply_to = ask(
"Message-ID to be used as In-Reply-To for the first email? ");
}
--
1.6.4.4
next prev parent reply other threads:[~2010-06-01 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 14:41 git send-email should always ask for in-reply-to Alexander Stein
2010-06-01 15:46 ` Matthieu Moy
2010-06-01 18:08 ` Alexander Stein [this message]
2010-06-10 17:08 ` [PATCH] send-email: Ask for in-reply message ID even if from and to is already known Alexander Stein
2010-06-10 17:18 ` Ævar Arnfjörð Bjarmason
2010-06-11 19:06 ` Junio C Hamano
2010-06-11 20:11 ` Alexander Stein
2010-06-10 22:28 ` Matthieu Moy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1275415730-15360-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de \
--to=alexander.stein@informatik.tu-chemnitz.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).