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>
Britton Leo Kerin committed
Jan 2, 2024 at 19:02 UTC
9cce3be2df18c6779a417c59d0f4c06b2ef9b4f3
1 file changed
+2
-2
Documentation/git-bisect.txt
+2
-2
@@ -17,7 +17,7 @@ The command takes various subcommands, and different options depending
17
on the subcommand:
18
19
git bisect start [--term-(new|bad)=<term-new> --term-(old|good)=<term-old>]
20
- [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<path>...]
20
+ [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
21
git bisect (bad|new|<term-new>) [<rev>]
22
git bisect (good|old|<term-old>) [<rev>...]
23
git bisect terms [--term-good | --term-bad]
@@ -299,7 +299,7 @@ Cutting down bisection by giving more parameters to bisect start
299
300
You can further cut down the number of trials, if you know what part of
301
the tree is involved in the problem you are tracking down, by specifying
302
-path parameters when issuing the `bisect start` command:
302
+pathspec parameters when issuing the `bisect start` command:
303
304
------------
305
$ git bisect start -- arch/i386 include/asm-i386