git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ian Hilt <ian.hilt@gmx.com>
Cc: Francis Galiegue <fg@one2team.com>,
	Git Mailing List <git@vger.kernel.org>,
	Pierre Habouzit <madcoder@debian.org>
Subject: Re: [PATCH] git send-email: edit recipient addresses with the  --compose flag
Date: Sun, 09 Nov 2008 21:18:38 -0800	[thread overview]
Message-ID: <7vbpwo88gh.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811091910570.21142@sys-0.hiltweb.site> (Ian Hilt's message of "Sun, 9 Nov 2008 19:38:30 -0500 (EST)")

Ian Hilt <ian.hilt@gmx.com> writes:

> On Sun, 9 Nov 2008, Junio C Hamano wrote:
>> Ian Hilt <ian.hilt@gmx.com> writes:
>> 
>> > On Sun, 9 Nov 2008, Francis Galiegue wrote:
>> >> Le Sunday 09 November 2008 13:59:48 Ian Hilt, vous avez écrit :
>> >> > +	if ($c_file =~ /^To:\s*+(.+)\s*\nCc:/ism) {
>> >> 
>> >> Greedy operators are only supported with perl 5.10 or more... I think it's a 
>> >> bad idea to use them...
>> ...
>> You expect something non-blank there anyway, so why not do:
>> 
>> 	To:\s*(\S.*?)\s*\n....
>
> That works.  Although, I seem to be missing Francis' point.  According
> to perlre, a quantified subpattern is "greedy".  So a "greedy operator"
> is any one of the standard quantified subpatterns.  The "+" and "?"
> modify its matching behavior.  And it seems to me that it _has_ to use a
> q.s. to work ...

The "perlre" documentation you are reading is from Perl 5.10.0; check
"perldelta" documentation next to it.

I think you are wrong in saying that "it _has_ to use".  Yes, you _can_
use possessive quantifiers to write that pattern (provided if you can
limit your users to Perl 5.10.0 or later), but you do _not_ have to (and I
just showed you how).  By not using the new feature, you can make it work
for people with older version of Perl.

Not everybody who uses git can upgrade their Perl to newer versions.  We
try to stick to "5.6.1 or later"; anything that is not available in 5.8
series is too new to be used outside the contrib/ area.

That's the point Francis raised that you missed.  

  reply	other threads:[~2008-11-10  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 12:59 [PATCH] git send-email: edit recipient addresses with the --compose flag Ian Hilt
2008-11-09 14:13 ` Francis Galiegue
2008-11-09 20:09   ` Ian Hilt
2008-11-09 22:09     ` Junio C Hamano
2008-11-10  0:38       ` Ian Hilt
2008-11-10  5:18         ` Junio C Hamano [this message]
2008-11-10 18:12           ` Ian Hilt
2008-11-10  7:49         ` Francis Galiegue
2008-11-10  8:08           ` Aristotle Pagaltzis
2008-11-11  1:49     ` Tait
2008-11-11 11:30       ` Francis Galiegue
2008-11-11 20:47         ` Ian Hilt
2008-11-11 20:53           ` Ian Hilt
2008-11-11 20:53           ` Francis Galiegue
2008-11-11 22:14           ` Tait
2008-11-10  7:57 ` Francis Galiegue
2008-11-10  7:59   ` Francis Galiegue

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=7vbpwo88gh.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=fg@one2team.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).