Lines Matching refs:issue
26 #. Make the Linux kernel regression tracking bot "regzbot" track the issue (this
32 when the issue started to happen::
44 description pointing to all places where the issue was reported, as
47 only fixing part of the issue that caused the regression, you may use
82 "regzbot" immediately start tracking the issue:
90 This tells regzbot the version range in which the issue started to happen;
118 * Point to all places where the issue was reported using "Closes:" tags::
123 If you are only fixing part of the issue, you may use "Link:" instead as
134 into the issue weeks, months, or years later. These tags are also crucial for
152 should be less than two. And it ought to be just a few days, if the issue is
162 latter concerns a severe issue (e.g. acute security vulnerability, data loss,
169 till the end of the cycle, as the issue might discourage or prevent users and
173 resolving an issue then might take longer than outlined below.
177 * Aim to mainline a fix within two or three days, if the issue is severe or
235 series, please evaluate at least briefly if the issue might happen in current
286 maintainer to mention the issue in his mainline pull request.
308 issue might better be dealt with in private, feel free to omit the list.
348 links to the patch description pointing to all reports about the issue fixed.
423 the issue or a fix are discussed -- for example the posting of a patch fixing
505 more. Maybe there's a serious security issue with how we did things,
570 like "serious security issue" etc that just forces us to make changes
762 previously benign behavior of that old issue.
773 consensus about the issue it exposed.