Searched refs:bisect (Results 1 – 23 of 23) sorted by relevance
9 二分（bisect）缺陷41 $ git bisect start45 $ git bisect bad [commit]52 - 使用以下任一与git bisect进行交互::54 $ git bisect good58 $ git bisect bad65 $ git bisect start67 $ git bisect good v4.875 - ``git-bisect`` 的手册页76 - `Fighting regressions with git bisect（用git bisect解决回归）[all …]
41 bug-bisect
805 “Documentation/translations/zh_CN/admin-guide/bug-bisect.rst”文档中进行了详细1193 特别关照”部分和文档“Documentation/translations/zh_CN/admin-guide/bug-bisect.rst”。
12 二分（bisect）缺陷44 $ git bisect start48 $ git bisect bad [commit]55 - 使用以下任一與git bisect進行交互::57 $ git bisect good61 $ git bisect bad68 $ git bisect start70 $ git bisect good v4.878 - ``git-bisect`` 的手冊頁79 - `Fighting regressions with git bisect（用git bisect解決回歸）[all …]
42 bug-bisect
806 「Documentation/translations/zh_TW/admin-guide/bug-bisect.rst」文檔中進行了詳細1194 特別關照」部分和文檔「Documentation/translations/zh_TW/admin-guide/bug-bisect.rst」。
35 - start bisect with [#f1]_::37 $ git bisect start41 $ git bisect bad [commit]45 $ git bisect good [commit]48 - interact with git bisect by using either::50 $ git bisect good54 $ git bisect bad63 $ git bisect start65 $ git bisect good v4.873 - The man page for ``git-bisect``[all …]
40 bug-bisect
1046 'Documentation/admin-guide/bug-bisect.rst' describes in detail. That process1574 the document 'Documentation/admin-guide/bug-bisect.rst' for details how to
19 TEST_START IF ${TEST} == bisect20 TEST_TYPE = bisect46 MIN_CONFIG = ${THIS_DIR}/config-bisect82 TEST_START IF ${TEST} == config-bisect
13 import bisect64 position = bisect.bisect(system_ram, phys_addr)70 position = bisect.bisect(pmem, phys_addr)
195 TEST_START IF ${RUN} == bisect199 TEST_TYPE = bisect
60 INCLUDE include/bisect.conf
91 INCLUDE include/bisect.conf
136 INCLUDE include/bisect.conf
184 都能正常构建和运行。使用 ``git bisect`` 来追踪问题的开发者可能会在任何时
187 都能正常構建和運行。使用 ``git bisect`` 來追蹤問題的開發者可能會在任何時
53 to review your changes, and to bisect any resulting problems.
124 comando "git bisect" viene usato per trovare delle regressioni; se il139 regressioni, "bisect" indicherà quest'ultima patch come causa del
136 trovato un problema usando ``git bisect``, per favore usate l'etichetta184 che usano ``git bisect`` per scovare i problemi potrebbero finire nel mezzo
3018 sub bisect { subroutine4444 bisect $i;
109 scenario when the "git bisect" tool is used to find regressions; if the
139 ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of185 series. Developers using ``git bisect`` to track down a problem can end up
Completed in 38 milliseconds