Re: [PATCH 5.9 000/757] 5.9.2-rc1 review

[Ronald Warsow <rwarsow@gmx.de>]

On 29.10.20 10:14, Greg KH wrote:
> On Tue, Oct 27, 2020 at 07:09:52PM +0100, Ronald Warsow wrote:
>> Hallo
>>
>> this rc1 runs here (pure Intel-box) without errors.
>> Thanks !
>>
>>
>> An RPC (I'm thinking about since some month)
>> ======
>>
>> Wouldn't it be better (and not so much add. work) to sort the
>> Pseudo-Shortlog towards subsystem/driver ?
>>
>> something like this:
>>
>> ...
>> usb: gadget: f_ncm: allow using NCM in SuperSpeed Plus gadgets.
>> usb: cdns3: gadget: free interrupt after gadget has deleted
>>
>>     Lorenzo Colitti <lorenzo@google.com>
>>     Peter Chen <peter.chen@nxp.com>
>> ...
>>
>>
>> Think of searching a bugfix in the shortlog.
>>
>> With the current layout I need to read/"visual grep" the whole log.
>>
>> With the new layout I'm able to jump to the "buggy" subsystem/driver and
>> only need to read that part of the log to get the info if the bug is
>> fixed or not yet
>
> Do you have an example script that generates such a thing?  If so, I'll
> be glad to look into it, but am not going to try to create it on my own,
> sorry.
>
> thanks,
>
> greg k-h
>

first of all: in the above mail it should read "RFC"


Surely, who get the most benefit of it (the layout) does the most work.
Agreed, I will see what I can do -I'm unsure -

Currently, I'm thinking that the data for your shortlog are coming from
a sort of an git query or so and it would just be an easy adjustment of
the query parameter.

This seems not to be the case ?

To get an idea if my knowledge is sufficing (I'm no developer):

Where do you get the data from to generate your shortlog ?

--
regards

Ronald