[CCing Konstantin] On 21.06.23 20:08, Linus Torvalds wrote: > On Wed, 21 Jun 2023 at 10:56, Linus Torvalds > <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> I'll just revert it for now. > > Btw, Thorsten, is there a good way to refer to the regzbot entry in a > commit message some way? I know about the email interface, but I'd > love to just be able to link to the regression entry. There is a separate page for each tracked regression: https://linux-regtracking.leemhuis.info/regzbot/regression/lore/GQUnKz2al3yke5mB2i1kp3SzNHjK8vi6KJEh7rnLrOQ24OrlljeCyeWveLW9pICEmB9Qc8PKdNt3w1t_g3-Uvxq1l8Wj67PpoMeWDoH8PKk=@proton.me/ FWIW, such pages existed earlier already, but before sending this reply I wanted to fix a related bug that changed the url slightly. One can find that link by clicking on "activity" in the regzbot webui (I need to find a better place for this link to make it more approachable :-/ ). And yes, in this case the URL sadly is rather long -- and the long msgid is only partly to blame. If we really want to link there more regularly I could work towards making that url shorter. That being said: I wonder if we really want to add these links to commit messages regularly. In case of this particular regression... > Now I just linked to the report in this thread. ...the thread with the report basically contains nearly everything relevant (expect a link to the commit with the revert; but in this case that's where the journey or a curious reader would start). But yes, for regressions with a more complex history it's different, as there the regzbot webui makes things a bit easier -- among others by directly pointing to patches in the same or other threads that otherwise are hard to find from the original thread, unless you know how to search for them on lore. I sometimes wonder if the real solution for this kind of problem would be some bot (regzbot? bugbot?) that does something similar to the pr-tracker-bot: 1) bot notices when a patch with a Link: or Closes: tag to a thread with the msgid <foo> is posted or applied to next, mainline, or stable 2) bot posts a reply to <foo> with a short msg like "a patch that links to this thread was (posted|merged); for details see <url>" That would solve a few things (that might or might not be worth solving): * bug reporters would become aware of the progress in case the developer forgets to CC them (which happens) * people that run into an issue and search for existing mailed reports on lore currently have no simple way to find fixes that are already under review or were applied somewhere already That together with lore is also more likely to be long-term stable than links to the regzbot webui. Ciao, Thorsten
