Lines Matching +full:use +full:- +full:case

1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
8 This document describes how to use a ``git bisect`` to find the source code
9 change that broke something -- for example when some functionality stopped
13 kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
17 care about the result -- for example, because the problem happens after the
28 use as pristine base at each bisection step; ideally, you have also worked out
29 a fully reliable and straight-forward way to reproduce the regression, too.*
38   Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
64    minutes more on testing in case your reproducer is unreliable.
68    test after this (roughly 10 steps)'. In that case go back to step 1.
71    is the first bad commit', then you have finished the bisection. In that case
75    mentioning the culprit's commit-id.
77    In case you missed Git's output, you can always run ``git bisect log`` to
85      git bisect log > ~/bisection-log
86      cp .config ~/bisection-config-culprit
90   codebase and check if that fixes your bug; if that is the case, it validates
95   to revert the change by specifying its commit-id::
97      git revert --no-edit cafec0cacaca0
100   commit. In that case, abandon the attempt. Do the same, if Git fails to revert
101   the culprit on its own because later changes depend on it -- at least unless
102   you bisected a stable or longterm kernel series, in which case you want to
109 Documentation/admin-guide/reporting-issues.rst.
113 ---------------------------
115 * The `man page for 'git bisect' <https://git-scm.com/docs/git-bisect>`_ and
116   `fighting regressions with 'git bisect' <https://git-scm.com/docs/git-bisect-lk2009.html>`_
118 * `Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_
124    end-of-content
129    want to contribute changes to the text -- but for copyright reasons please CC
130    linux-doc@vger.kernel.org and 'sign-off' your contribution as
131    Documentation/process/submitting-patches.rst explains in the section 'Sign
132    your work - the Developer's Certificate of Origin'.
134    This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
135    of the file. If you want to distribute this text under CC-BY-4.0 only,
136    please use 'The Linux kernel development community' for author attribution
138 …rnel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst
142    is available under CC-BY-4.0, as versions of this text that were processed
144    files which use a more restrictive license.