Home
last modified time | relevance | path

Searched refs:bisect (Results 1 – 24 of 24) sorted by relevance

/linux/Documentation/translations/zh_CN/admin-guide/
H A Dbug-bisect.rst3 :Original: :doc:`../../../admin-guide/bug-bisect`
9 二分（bisect）缺陷
41 $ git bisect start
45 $ git bisect bad [commit]
49 $ git bisect good [commit]
52 - 使用以下任一与git bisect进行交互::
54 $ git bisect good
58 $ git bisect bad
61 - 在一些交互之后，git bisect将给出可能导致缺陷的变更集。
65 $ git bisect start
[all …]
H A Dindex.rst41 bug-bisect
H A Dreporting-regressions.rst137 和 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst （详细）中所
H A Dreporting-issues.rst800 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 文档中进行了详细
1200 特别关照”部分和文档 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 。
/linux/Documentation/translations/zh_TW/admin-guide/
H A Dbug-bisect.rst5 :Original: :doc:`../../../admin-guide/bug-bisect`
12 二分（bisect）缺陷
44 $ git bisect start
48 $ git bisect bad [commit]
52 $ git bisect good [commit]
55 - 使用以下任一與git bisect進行交互::
57 $ git bisect good
61 $ git bisect bad
64 - 在一些交互之後，git bisect將給出可能導致缺陷的變更集。
68 $ git bisect start
[all …]
H A Dindex.rst44 bug-bisect
H A Dreporting-regressions.rst137 和 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst （詳細）中所
H A Dreporting-issues.rst801 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 文檔中進行了詳細
1201 特別關照”部分和文檔 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 。
/linux/Documentation/admin-guide/
H A Dbug-bisect.rst8 This document describes how to use a ``git bisect`` to find the source code
13 kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
34 git bisect start
35 git bisect good v6.0
36 git bisect bad v6.1
48 bisection a later change resolves. In such cases run ``git bisect skip`` and
55 git bisect good
59 git bisect bad
77 In case you missed Git's output, you can always run ``git bisect log`` to
85 git bisect log > ~/bisection-log
[all …]
H A Dreporting-regressions.rst159 Documentation/admin-guide/bug-bisect.rst. It might sound like a lot of work, but
/linux/tools/testing/ktest/examples/include/
H A Dbisect.conf19 TEST_START IF ${TEST} == bisect
20 TEST_TYPE = bisect
46 MIN_CONFIG = ${THIS_DIR}/config-bisect
82 TEST_START IF ${TEST} == config-bisect
/linux/tools/testing/ktest/examples/
H A Dcrosstests.conf195 TEST_START IF ${RUN} == bisect
199 TEST_TYPE = bisect
H A Dtest.conf60 INCLUDE include/bisect.conf
H A Dkvm.conf91 INCLUDE include/bisect.conf
H A Dvmware.conf136 INCLUDE include/bisect.conf
/linux/Documentation/translations/zh_TW/process/
H A Dsubmitting-patches.rst155 都能正常構建和運行。使用 ``git bisect`` 來追蹤問題的開發者可能會在任何地方分
/linux/Documentation/translations/zh_CN/process/
H A Dsubmitting-patches.rst154 都能正常构建和运行。使用 ``git bisect`` 来追踪问题的开发者可能会在任何地方分
/linux/Documentation/translations/ja_JP/
H A DSubmittingPatches135 特定のコミットで導入された不具合を修正する場合（例えば ``git bisect`` で原因となった
/linux/Documentation/hwmon/
H A Dsubmitting-patches.rst52 to review your changes, and to bisect any resulting problems.
/linux/tools/testing/ktest/
H A Dktest.pl3094 sub bisect { subroutine
4614 bisect $i;
/linux/Documentation/process/
H A Dsubmitting-patches.rst146 ``git bisect``, please use the 'Fixes:' tag with at least the first 12
192 series. Developers using ``git bisect`` to track down a problem can end up
/linux/Documentation/translations/sp_SP/process/
H A Dsubmitting-patches.rst154 encontró un problema usando ``git bisect``, utilice la etiqueta 'Fixes:'
203 cada parche en la serie. Los desarrolladores que usan ``git bisect``
H A Dhandling-regressions.rst100 haya identificado el commit causante con 'bisect'.
/linux/
H A DMAINTAINERS7552 F: Documentation/admin-guide/bug-bisect.rst
7555 F: Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst