Home
last modified time | relevance | path

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

/Linux-v6.1/Documentation/translations/zh_CN/admin-guide/
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 …]
Dindex.rst42 bug-bisect
Dreporting-regressions.rst137 和 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst (详细)中所
Dreporting-issues.rst800 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 文档中进行了详细
1200 特别关照”部分和文档 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst 。
/Linux-v6.1/Documentation/translations/zh_TW/admin-guide/
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 …]
Dindex.rst42 bug-bisect
Dreporting-issues.rst806 「Documentation/translations/zh_TW/admin-guide/bug-bisect.rst」文檔中進行了詳細
1194 特別關照」部分和文檔「Documentation/translations/zh_TW/admin-guide/bug-bisect.rst」。
/Linux-v6.1/Documentation/admin-guide/
Dbug-bisect.rst35 - start bisect with [#f1]_::
37 $ git bisect start
41 $ git bisect bad [commit]
45 $ git bisect good [commit]
48 - interact with git bisect by using either::
50 $ git bisect good
54 $ git bisect bad
57 - After some interactions, git bisect will give you the changeset that
63 $ git bisect start
64 $ git bisect bad # Current version is bad
[all …]
Dindex.rst41 bug-bisect
Dreporting-regressions.rst159 Documentation/admin-guide/bug-bisect.rst. It might sound like a lot of work, but
Dreporting-issues.rst1031 Documentation/admin-guide/bug-bisect.rst describes in detail. That process
1560 the document Documentation/admin-guide/bug-bisect.rst for details how to
/Linux-v6.1/tools/testing/ktest/examples/include/
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-v6.1/tools/perf/scripts/python/
Dmem-phys-addr.py13 import bisect
64 position = bisect.bisect(system_ram, phys_addr)
70 position = bisect.bisect(pmem, phys_addr)
/Linux-v6.1/tools/testing/ktest/examples/
Dcrosstests.conf195 TEST_START IF ${RUN} == bisect
199 TEST_TYPE = bisect
Dtest.conf60 INCLUDE include/bisect.conf
Dkvm.conf91 INCLUDE include/bisect.conf
Dvmware.conf136 INCLUDE include/bisect.conf
/Linux-v6.1/Documentation/translations/zh_TW/process/
Dsubmitting-patches.rst185 都能正常構建和運行。使用 ``git bisect`` 來追蹤問題的開發者可能會在任何時
/Linux-v6.1/Documentation/translations/zh_CN/process/
Dsubmitting-patches.rst154 都能正常构建和运行。使用 ``git bisect`` 来追踪问题的开发者可能会在任何地方分
/Linux-v6.1/Documentation/hwmon/
Dsubmitting-patches.rst52 to review your changes, and to bisect any resulting problems.
/Linux-v6.1/Documentation/translations/it_IT/process/
D5.Posting.rst123 comando "git bisect" viene usato per trovare delle regressioni; se il
138 regressioni, "bisect" indicherà quest'ultima patch come causa del
Dsubmitting-patches.rst149 trovato un problema usando ``git bisect``, per favore usate l'etichetta
197 che usano ``git bisect`` per scovare i problemi potrebbero finire nel mezzo
/Linux-v6.1/tools/testing/ktest/
Dktest.pl3018 sub bisect { subroutine
4444 bisect $i;
/Linux-v6.1/Documentation/process/
Dsubmitting-patches.rst138 ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
184 series. Developers using ``git bisect`` to track down a problem can end up
D5.Posting.rst108 scenario when the "git bisect" tool is used to find regressions; if the