On Fri, May 27, 2022 at 08:40:14AM -0700, Luis Chamberlain wrote: > On Fri, May 27, 2022 at 03:24:02PM +0300, Amir Goldstein wrote: > > On Fri, May 27, 2022 at 12:08 PM Dave Chinner <david@xxxxxxxxxxxxx> wrote: > > > Backport candidate: yes. Severe: absolutely not. > > In the future, if you are writing a cover letter for an improvement > > series or internal pull request and you know there is a backport > > candidate inside, if you happen to remember to mention it, it would > > be of great help to me. > > Amir, since you wrote a tool enhancement to scrape for possible > candidates, *if* we defined some sort of meta-data to describe > this sort of stuff on the cover letter: > > Backport candidate: yes. Severe: absolutely not > > It would be useful when scraping. Therefore, leaving the effort > to try to backport / feasibility to others. This would be different > than a stable Cc tag, as those have a high degree of certainty. > > How about something like: > > Backport-candidate: yes > Impact: low This particular patch (because we've recently hit it internally too) would have been one of those: Stable-Soak: January 2022 patches that I was talking about. --D > Luis
