git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Allen Hubbe <allenbh@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/9] send-email: further document missing sendmail aliases functionality
Date: Mon, 1 Jun 2015 14:22:36 -0400	[thread overview]
Message-ID: <20150601182236.GA28030@flurp.local> (raw)
In-Reply-To: <CAJ80sau0GeeFxFZYsEE=uupfPqJ=vRZfNRuNd0qRJPDNvnbMPw@mail.gmail.com>

On Mon, Jun 01, 2015 at 07:43:08AM -0400, Allen Hubbe wrote:
> On May 31, 2015 at 6:29 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> > Sendmail aliases[1] supports expansion to a file ("/path/name") or
> > pipe ("|command"), as well as file inclusion (":include: /path/name"),
> > however, our implementation does not support such functionality.
>
> According to the documentation, the parser should print a warning for
> any explicitly unsupported constructs.  These are now explicitly
> unsupported, so the parser should warn on |, /, and :include: .
> Perhaps the lines that match should be ignored like the others, too.

Indeed. I had that in mind and then promptly forgot about it. Here's a
follow-on patch:

--- >8 ---
From: Eric Sunshine <sunshine@sunshineco.com>
Subject: [PATCH 10/9] send-email: further warn about unsupported sendmail aliases features

The sendmail aliases parser diagnoses unsupported features and
unrecognized lines. For completeness, also warn about unsupported
redirection to "/path/name" and "|command", as well as ":include:".

Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
---
 git-send-email.perl | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/git-send-email.perl b/git-send-email.perl
index eb1d678..ae9f869 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -492,6 +492,10 @@ sub parse_sendmail_alias {
 	local $_ = shift;
 	if (/"/) {
 		print STDERR "warning: sendmail alias with quotes is not supported: $_\n";
+	} elsif (/:include:/) {
+		print STDERR "warning: `:include:` not supported: $_\n";
+	} elsif (/[\/|]/) {
+		print STDERR "warning: `/file` or `|pipe` redirection not supported: $_\n";
 	} elsif (/^(\S+?)\s*:\s*(.+)$/) {
 		my ($alias, $addr) = ($1, $2);
 		$aliases{$alias} = [ split_addrs($addr) ];
-- 
2.4.2.538.g5f4350e

--- >8 ---

  reply	other threads:[~2015-06-01 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 22:29 [PATCH 0/9] send-email: add sendmail aliases line continuation support Eric Sunshine
2015-05-31 22:29 ` [PATCH 1/9] send-email: further document missing sendmail aliases functionality Eric Sunshine
2015-06-01 11:43   ` Allen Hubbe
2015-06-01 18:22     ` Eric Sunshine [this message]
2015-06-01 22:44       ` Allen Hubbe
2015-05-31 22:29 ` [PATCH 2/9] send-email: visually distinguish sendmail aliases parser warnings Eric Sunshine
2015-05-31 22:29 ` [PATCH 3/9] send-email: drop noise comments which merely repeat what code says Eric Sunshine
2015-05-31 22:29 ` [PATCH 4/9] send-email: fix style: cuddle 'elsif' and 'else' with closing brace Eric Sunshine
2015-05-31 22:29 ` [PATCH 5/9] send-email: refactor sendmail aliases parser Eric Sunshine
2015-05-31 22:29 ` [PATCH 6/9] send-email: simplify sendmail aliases comment and blank line recognizer Eric Sunshine
2015-06-01  3:30   ` Eric Sunshine
2015-05-31 22:29 ` [PATCH 7/9] send-email: implement sendmail aliases line continuation support Eric Sunshine
2015-05-31 22:29 ` [PATCH 8/9] t9001: refactor sendmail aliases test infrastructure Eric Sunshine
2015-05-31 22:29 ` [PATCH 9/9] t9001: add sendmail aliases line continuation tests Eric Sunshine
2015-06-01 11:49 ` [PATCH 0/9] send-email: add sendmail aliases line continuation support Allen Hubbe

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=20150601182236.GA28030@flurp.local \
    --to=sunshine@sunshineco.com \
    --cc=allenbh@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).