git gcc-commit-mklog doesn't extract PR number to ChangeLog

[Martin Liška]

On 6/10/21 8:25 AM, Xionghu Luo wrote:
> 
> 
> On 2021/6/10 14:17, Martin Liška wrote:
>> On 6/10/21 7:22 AM, Xionghu Luo wrote:
>>> Sorry, should be sent to this mail-list.
>>>
>>>
>>> On 2021/6/10 11:31, Xionghu Luo via Gcc-patches wrote:
>>>> Hi,
>>>> I noticed that the "git gcc-commit-mklog" command doesn't extract PR
>>>> number from title to ChangeLog automatically, then the committed patch
>>>> doesn't update the related bugzilla PR website after check in the patch?
>>
>> Hello.
>>
>> Yes, we currently only support automatic extraction from comments from
>> test-cases.
>> How does your commit title look like? Note that we require bugzilla
>> components
>> being part of PR entry, which is not commonly used in git titles due to
>> length
>> limitation.
>>
>>>> Martin, what's your opinion about this since you are much familar about
>>>> this? Thanks.
>>
>> Please provide few examples of existing commits?
> 
> Thanks. For example:
> 
> rs6000: Support doubleword swaps removal in rot64 load store [PR100085]
> 
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f700e4b0ee3ef53b48975cf89be26b9177e3a3f3

I see. Well, note that gcc-commit-mklog is calling ./contrib/mklog.py when you're
going to write a commit message.

How can the script get [PRnnnn] from a non-existing title. Please show me your
complete workflow.

Thanks,
Martin

> 
> 
>>
>> Thanks,
>> Martin
>>
>>>>
>>>>
>>>
>>
>