kernel
/
git
mirror of https://git.kernel.org/pub/scm/git/git.git
1
0
Fork 0
Code Releases Activity

doc: refer to pathspec instead of path 

Signed-off-by: Britton Leo Kerin <britton.kerin@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Britton Leo Kerin 2024-01-02 19:02:07 -09:00 committed by Junio C Hamano
parent 3dbb69e1f2
commit 9cce3be2df
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/git-bisect.txt
View File

@ -17,7 +17,7 @@ The command takes various subcommands, and different options depending
on the subcommand: on the subcommand:


git bisect start [--term-(new|bad)=<term-new> --term-(old|good)=<term-old>] git bisect start [--term-(new|bad)=<term-new> --term-(old|good)=<term-old>]
[--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<path>...] [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
git bisect (bad|new|<term-new>) [<rev>] git bisect (bad|new|<term-new>) [<rev>]
git bisect (good|old|<term-old>) [<rev>...] git bisect (good|old|<term-old>) [<rev>...]
git bisect terms [--term-good | --term-bad] git bisect terms [--term-good | --term-bad]
@ -299,7 +299,7 @@ Cutting down bisection by giving more parameters to bisect start


You can further cut down the number of trials, if you know what part of You can further cut down the number of trials, if you know what part of
the tree is involved in the problem you are tracking down, by specifying the tree is involved in the problem you are tracking down, by specifying
path parameters when issuing the `bisect start` command: pathspec parameters when issuing the `bisect start` command:


------------ ------------
$ git bisect start -- arch/i386 include/asm-i386 $ git bisect start -- arch/i386 include/asm-i386