From: Junio C Hamano <gitster@pobox.com>
To: Allen Hubbe <allenbh@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-send-email.perl: Add sendmail aliases support
Date: Thu, 21 May 2015 14:19:46 -0700 [thread overview]
Message-ID: <xmqq617liq6l.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJ80satMSCGydLRb5k=xpSqxXSBL=_T7nsHEz3jsuFV9MdmmtA@mail.gmail.com> (Allen Hubbe's message of "Thu, 21 May 2015 16:48:15 -0400")
Allen Hubbe <allenbh@gmail.com> writes:
> The diff doesn't show enough context to include this comment:
>
> my %parse_alias = (
> # multiline formats can be supported in the future
> ...
>
> I can't be sure the author's intent, but my interpretation is such.
> The parsers do not support multiline, even though the format might
> allow it by definition. Another interpretation could be, no multiline
> formats allowed, or, the first person to add a multiline format should
> remove this comment.
I think that comment were only meant to apply to the first one, mutt.
In any case, you should read it this way:
Some formats may support multi-line; this parser back when the
comment was written did not support an alias file that uses such
a feature, but it is OK to make it support them in the future.
After all, these subs are slurping from $fh and doing the parsing
themselves, so they are free to do multi-line if they wanted to.
It's not like there is a calling function that feeds input line by
line after splitting a logically continued line into two (and if
that were the case, supporting multi-line format may become harder
or even impossible).
And as I said, it is OK not to support ones that have folded lines.
All I was saying was that we should not SILENTLY fail or do a wrong
thing when we find something we do not support.
prev parent reply other threads:[~2015-05-21 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 18:51 [PATCH] git-send-email.perl: Add sendmail aliases support Allen Hubbe
2015-05-21 20:19 ` Junio C Hamano
2015-05-21 20:48 ` Allen Hubbe
2015-05-21 21:05 ` Eric Sunshine
2015-05-21 21:30 ` Allen Hubbe
2015-05-21 21:38 ` Junio C Hamano
2015-05-21 22:45 ` Allen Hubbe
2015-05-21 21:19 ` Junio C Hamano [this message]
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=xmqq617liq6l.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=allenbh@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.