From: Jan Engelhardt <jengelh@medozas.de>
To: git@vger.kernel.org
Subject: [PATCH] send-email: confirm on empty mail subjects
Date: Wed, 5 Aug 2009 18:49:54 +0200 [thread overview]
Message-ID: <1249490994-23455-1-git-send-email-jengelh@medozas.de> (raw)
When the user forgot to enter a subject in a compose session,
send-email will now inquire whether this is really intended, similar
to what the Alpine MUA does when a subject is absent.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
---
git-send-email.perl | 25 ++++++++++++++++++++-----
1 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/git-send-email.perl b/git-send-email.perl
index d508f83..7d56fba 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -553,11 +553,26 @@ EOT
}
close(C);
- if ($annotate) {
- do_edit($compose_filename, @files);
- } else {
- do_edit($compose_filename);
- }
+ my $re_edit = 0;
+ do {
+ if ($annotate) {
+ do_edit($compose_filename, @files);
+ } else {
+ do_edit($compose_filename);
+ }
+
+ open(C, "<", $compose_filename) ||
+ die "Failed to open $compose_filename: $!";
+ if (grep(/^Subject:\s*$/i, <C>)) {
+ my $r = ask("No Subject, send anyway? ".
+ "([y]es|[n]o|[e]dit again): ",
+ valid_re => qr/^[yne]/i,
+ default => "n");
+ $re_edit = lc(substr($r, 0, 1)) eq "e";
+ exit(0) if lc(substr($r, 0, 1)) eq "n";
+ }
+ close C;
+ } while ($re_edit);
open(C2,">",$compose_filename . ".final")
or die "Failed to open $compose_filename.final : " . $!;
--
1.6.4
next reply other threads:[~2009-08-05 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 16:49 Jan Engelhardt [this message]
2009-08-06 6:25 ` [PATCH] send-email: confirm on empty mail subjects Junio C Hamano
2009-08-24 17:27 ` Jan Engelhardt
2009-08-24 18:19 ` Junio C Hamano
2009-08-25 16:27 ` Jan Engelhardt
2009-08-25 17:35 ` Junio C Hamano
2009-09-11 23:27 ` Junio C Hamano
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=1249490994-23455-1-git-send-email-jengelh@medozas.de \
--to=jengelh@medozas.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.
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).