On Thu, Sep 17, 2020 at 10:00:44AM +0200, Borislav Petkov wrote: > On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote: > > The 2nd type is this one, which is a summarized report of head > > to provide an overview. Most of time, repo owner can receive the > > bisected mail. For this time, the issue is reported against peterz-queue > > repo which has this 767d46ab56 head firstly. Since the head later appears > > in tip, we just gather all issues and send the summary to tip related > > recipients. But no more bisected mail. > > Yeah, but that second report is not very helpful because nowhere it says > it is a summary and nowhere it has that link you pasted above so that > some other maintainer can go look. > > Always put yourself in the recipient's shoes and ask yourself: "what can > the recipient do with this report and does it have everything in there > required to be able to reproduce the issue?" > > If not, then it needs changing. thanks for the advice. We will provide update in 1-2 weeks for the progress to make the report more informative and useful.
> > > We will consider how to show useful produce info in summary report as > > the feedback here, which is quite useful, such like pointing to the > > bisected mail. This would take some time, and we will add to our TODO > > as high priority. > > Yes, that would be much appreciated. You can also tag your reports with > a unique hash which is then in an URL so that one can go and download the > .config and what else is needed. For example... > > Thx. > > -- > Regards/Gruss, > Boris. > > https://people.kernel.org/tglx/notes-about-netiquette
