Lines Matching +full:straight +full:- +full:forward
1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
7 *We don't cause regressions* -- this document describes what this "first rule of
9 Documentation/admin-guide/reporting-regressions.rst, which covers the topic from a
21 loop by immediately sending at least a brief "Reply-all" with the list
24 * Forward or bounce any reports submitted in bug trackers to the list.
30 introduced v5.13..v5.14-rc1``. If not, send a reply (with the regressions
39 #regzbot introduced: v5.13..v5.14-rc1
45 mandated by Documentation/process/submitting-patches.rst and
58 -----------------------------------
69 it into the loop by sending at least a brief "Reply-all" with the list CCed;
73 * If a report submitted in a bug tracker hits your Inbox, forward or bounce it
76 Documentation/admin-guide/reporting-issues.rst.
85 #regzbot ^introduced: v5.13..v5.14-rc1
88 you can specify a range using commit-ids as well or state a single commit-id
111 remember to do what Documentation/process/submitting-patches.rst,
113 Documentation/process/stable-kernel-rules.rst already explain in more detail:
146 severe or affects many users -- either in general or in prevalent
171 bothering many users -- either in general or in prevalent conditions like a
181 regression is something people can live with easily for a while -- like a
192 variant later: that should be straight-forward, as most of the code went
201 tangly. Do the same in precarious or urgent cases -- especially if the
205 * For urgent regressions, consider asking Linus to pick up the fix straight
213 the fix straight from the list. He then himself can make the call and when
229 mainline as well -- and if that seems likely, take hold of the report. If in
234 mainline; when appropriate thus involve Linus to fast-track the fix (see
247 Linus, ideally with them being in linux-next at least briefly. Hence, if a
254 of regression fixes. Thus evaluate if skipping linux-next is an option for
257 weekends -- especially when the fix is marked for backporting.
261 ----------------------------------------------------------------
284 Check out Documentation/admin-guide/reporting-regressions.rst, it covers a lot
305 ------------------------------------------
348 Torvalds partly rely on regzbot's tracking in their work -- for example when
357 important unexpectedly comes up -- for example a bigger problem in the Linux
366 Check `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_
370 few hours before Linus usually publishes new (pre-)releases.
376 repositories of linux-next, mainline, and stable/longterm.
417 the issue or a fix are discussed -- for example the posting of a patch fixing
435 #regzbot fixed-by: 1f2e3d4c5d
439 #regzbot dup-of: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/
448 More detailed and up-to-date information about the Linux
451 contains a `getting started guide <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_star…
452 and `reference documentation <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md>`_
456 ----------------------------------
461 * From `2017-10-26 (1/2)
474 - we don't cause regressions
484 * From `2017-10-26 (2/2)
543 obviously have to fix up all the in-kernel users of that API. Nobody
549 * From `2020-05-21
550 …<https://lore.kernel.org/all/CAHk-=wiVi7mSrsMP=fLXQrXK_UimybW=ziLOwSzFTtoXUacWVQ@mail.gmail.com/>`…
563 Now, reality is never entirely black-and-white. So we've had things
575 code was in staging or because the man-page said something else) is
582 any changes to an API you like - as long as nobody notices.
589 * From `2017-11-05
590 …<https://lore.kernel.org/all/CA+55aFzUvbGjD8nQ-+3oiMBx14c_6zOj2n7KLN3UsJ-qsd4Dcw@mail.gmail.com/>`…
606 * From `2018-08-03
643 the point. As far as the USER was concerned, it wasn't buggy - it
647 maybe it worked because the user didn't notice - again, it doesn't
667 other programs at all. It is absolutely required, because flag-days
678 * From `2021-06-05
679 …<https://lore.kernel.org/all/CAHk-=wiUVqHN76YUwhkjZzwTdjMMJf_zN4+u7vEJjmEGh3recw@mail.gmail.com/>`…
688 * From `2011-05-06 (1/3)
689 <https://lore.kernel.org/all/BANLkTim9YvResB+PwRp7QTK-a5VNg2PvmQ@mail.gmail.com/>`_::
694 parse it wrongly - see the fairly recent example of adding uuid's to
711 From `2011-05-06 (2/3)
717 From `2011-05-06 (3/3)
722 …* From `2012-07-06 <https://lore.kernel.org/all/CA+55aFwnLJ+0sjx92EGREGTWOx84wwKaraSzpTNJwPVV8edw8…
730 * From `2019-09-15
731 …<https://lore.kernel.org/lkml/CAHk-=wiP4K8DRJWsCo=20hn_6054xBamGKF2kPgUzpB5aMaofA@mail.gmail.com/>…
733 One _particularly_ last-minute revert is the top-most commit (ignoring
740 improved IO patterns it caused then ended up revealing a user-visible
751 The point here being that we revert based on user-reported _behavior_,
753 The problem was really pre-existing, and it just didn't happen to
758 And never fear, we'll re-introduce the fix that improved on the IO
766 re-introduced (perhaps even backported as a stable patch) once we have
769 Take-away from the whole thing: it's not about whether you change the
770 kernel-userspace ABI, or fix a bug, or about whether the old code
779 end-of-content
781 This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
782 of the file. If you want to distribute this text under CC-BY-4.0 only,
785 …rg/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/handling-regressions.rst
788 is available under CC-BY-4.0, as versions of this text that were processed