Baruch Siach <bar...@tkos.co.il> writes:
> Hi Junio,
>
> On Thu, Apr 04 2019, Junio C. Hamano wrote:
>> Baruch Siach <bar...@tkos.co.il> writes:
>>
>>>> Independently, I think it makes sense to do something like
>>>>
>>>> /^([a-z][a-z-]*-by|Cc): (.*)/i
>>>>
>>>> to tighten the match to exclude a non-trailer; that would have been
>>>> sufficient for the original case that triggered this thread.
>>>
>>> Is there anything I need to do more to get this fix applied for the next
>>> git release?
>>
>> Get "this" fix applied? I think we should tighten the regexp to
>> exclude a non-trailer, which would have been sufficient for the
>> original case without anything else in "this" fix. So in short, I
>> do not think "this" fix won't be applied without further tweaking
>> ;-)
>
> This is exactly what "this" patch (referenced in the title of "this"
> thread) is doing:
>
>
> https://public-inbox.org/git/eec56beab016182fb78fbd367fcfa97f2ca6a5ff.1552764410.git.bar...@tkos.co.il/
>
> Am I missing something?
That is totally outside of the in-reply-to/references trail of your
ping message, and what I saw in the message you were quoting in your
'ping' was
>> $message .= $_;
>> - if (/^([a-z-]*-by|Cc): (.*)/i) {
>> + if (!$in_patch && /^([a-z-]*-by|Cc): (.*)/i) {
>> chomp;
which is a lot looser than the suggested "the beginning must be
alpha" pattern.
