Python based regex - POC - v2
Carlos O'Donell
carlos@redhat.com
Mon Nov 2 16:52:47 GMT 2026
On 10/21/26 1:53 PM, Sachin Monga wrote:
> PFA the v2 as mentioned in the mail below.
>
> If you've any suggestions then please do use the same mail thread.
>
> Regards,
> Sachin.
>
> On 21/10/26 12:08 am, Sachin Monga wrote:
>>
>> Hi Carlos/All,
>>
>> Attached is the POC document proposing replacement regular expressions for the AdaCore server-side git hook, for use as bugspray's |git_log_mentions_regexes|.
>>
>> Summary of what's in it:
>>
>> * The expression currently in production misses more than 60% of glibc's bug references. Measured across glibc commit history.
>> * The main cause is the leading |\s|, which cannot cross a bracket — so |[BZ #34532]|, glibc's most common form, never matches. Two further defects are documented.
>> * The proposal is a set of small, separately commented expressions rather than one — one set per project.
>> * A Python test script with 51 sample commit messages is included, along with its output. All 51 behave as expected.
>>
>>
>> This is v1 of the document and I am working on v2 now which will include the below 3 additions.
>> a) Component name in binutils should not matter while posting on bug number. b) The v1 bug# is restricted to accept only uptill 6 digits and not beyond that. I'll remove this (basically remove !\d part) c) Returning multiple bug# (eg. (bug 12345, bug 23456))
>>
>> Suggestions are welcome.
>>
>> Regards,
>> Sachin.
>>
>>
I'm reviewing this, but didn't finish my review last week.
--
Cheers,
Carlos.
More information about the Libc-alpha
mailing list