Lines Matching full: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
79 "regzbot" immediately start tracking the issue:
87    This tells regzbot the version range in which the issue started to happen;
115  * Point to all places where the issue was reported using "Link:" tags::
127 into the issue weeks, months, or years later. These tags are also crucial for
137 running into the issue; nevertheless developers need to take enough time and
159    free to delegate the work to the stable team, if the issue probably at no
176    reason -- for example, if the issue is likely to affect many users of the
182    the issue was introduced in either:
196    from running Linux (unless it's an issue in the current development cycle,
235 maintainer to mention the issue in his mainline pull request.
257 issue might better be dealt with in private, feel free to omit the list.
297 "Link:" tags to the patch description pointing to all reports about the issue
373    the issue or a fix are discussed -- for example the posting of a patch fixing
455        more. Maybe there's a serious security issue with how we did things,
520        like "serious security issue" etc that just forces us to make changes
712        previously benign behavior of that old issue.
723        consensus about the issue it exposed.