Lines Matching full:introduced

30       introduced v5.13..v5.14-rc1``. If not, send a reply (with the regressions
34        #regzbot ^introduced 1f2e3d4c5b6a
39        #regzbot introduced: v5.13..v5.14-rc1
82    ``#regzbot introduced 1f2e3d4c5b6a``. If not, send a reply (with the
85        #regzbot ^introduced: v5.13..v5.14-rc1
91    Note the caret (^) before the "introduced": it tells regzbot to treat the
100        #regzbot introduced: 1f2e3d4c5b6a
162  * Try to resolve any regressions introduced in the current development before
182    the issue was introduced in either:
292 introduced`` command outlined above; if they don't do that, someone else can
293 take care of that using ``#regzbot ^introduced``.
357 One such command is ``#regzbot introduced <version or commit>``, which makes
359 already described above; ``#regzbot ^introduced <version or commit>`` is another
365 of the `introduced` commands or in replies to the mail that used one of them
618        ARGUMENT if that bug fix broke a user setup. You actually introduced a
710        trigger before. The better IO patterns introduced by the change just
722        re-introduced (perhaps even backported as a stable patch) once we have