From: Junio C Hamano <gitster@pobox.com>
To: Ian Hilt <ian.hilt@gmx.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Pierre Habouzit <madcoder@debian.org>
Subject: Re: [PATCH v2] Edit recipient addresses with the --compose flag
Date: Thu, 13 Nov 2008 19:31:39 -0800 [thread overview]
Message-ID: <7v7i77f0f8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811132013530.6125@sys-0.hiltweb.site> (Ian Hilt's message of "Thu, 13 Nov 2008 21:10:43 -0500 (EST)")
Ian Hilt <ian.hilt@gmx.com> writes:
> On Wed, 12 Nov 2008, Junio C Hamano wrote:
>> Ian Hilt <ian.hilt@gmx.com> writes:
>>
>> > Sometimes specifying the recipient addresses can be tedious on the
>> > command-line. This commit allows the user to edit the recipient
>> > addresses in their editor of choice.
>> >
>> > Signed-off-by: Ian Hilt <ian.hilt@gmx.com>
>> > ---
>> > Here's an updated commit with improved regex's from Junio and Francis.
>>
>> This heavily depends on Pierre's patch, so I am CC'ing him for comments.
>> Until his series settles down, I cannot apply this anyway.
>
> I didn't realize this was such a bad time to submit this patch.
It is not a bad time. I just won't be able to apply it right away, but
people (like Pierre) who are interested in send-email enhancement can help
improving your patch by reviewing.
>> Why does the user must keep "Cc:" in order for this new code to pick up
>> the list of recipients? ...
>>
>> cc = "Cc:" address-list CRLF
>> bcc = "Bcc:" (address-list / [CFWS]) CRLF
>> address-list = (address *("," address)) / obs-addr-list
>
> I think you're mistaken here. It is entirely possible to delete the Cc
> and Bcc lines with no ill effect.
You have this piece of code
>> > + if ($c_file =~ /^To:\s*(\S.+?)\s*\nCc:/ism) {
>> > + @tmp_to = get_recipients($1);
>> > + }
to pick up the "To: " addressees. If your user deletes Cc: line, would
that regexp still capture them in @tmp_to? How?
> determine if $cc is equal to ''. If it's not, then it will use it.
Ah, somehow I thought C2 you are writing into (message.final) was used as
the final payload, but you are right. The foreach () loop at the toplevel
reads them and interprets them.
>> I think the parsing code you introduced simply suck. Why isn't it done as
>> a part of the main loop to read the same file that already exists?
>
> Multiline recipient fields.
So you were trying to handle folded headers after all, I see.
But if you were to go that route, I think you are much better off doing so
by enabling the header folding for all the header lines in the while (<C>)
loop that currently reads one line at a time.
I however hove to wonder why we are not using any canned e-mail header
parser for this part of the code. Surely there must be a widely used one
that everybody who writes Perl uses???
next prev parent reply other threads:[~2008-11-14 3:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 2:50 [PATCH v2] Edit recipient addresses with the --compose flag Ian Hilt
2008-11-13 3:18 ` Junio C Hamano
2008-11-14 2:10 ` Ian Hilt
2008-11-14 3:31 ` Junio C Hamano [this message]
2008-11-14 16:58 ` Ian Hilt
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=7v7i77f0f8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ian.hilt@gmx.com \
--cc=madcoder@debian.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).