Johannes Sixt <j...@kdbg.org> writes: > Am 26.01.2017 um 19:30 schrieb marcandre.lur...@redhat.com: >> From: Marc-André Lureau <marcandre.lur...@redhat.com> >> >> It looks like it can do it. >> >> Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com> >> --- >> git-bisect.sh | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/git-bisect.sh b/git-bisect.sh >> index ae3cb013e..b0bd604d4 100755 >> --- a/git-bisect.sh >> +++ b/git-bisect.sh >> @@ -1,5 +1,6 @@ >> #!/bin/sh >> >> +SUBDIRECTORY_OK=Yes >> >> USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|replay|log|run]' >> LONG_USAGE='git bisect help >> print this long help message. >> > > Does it also work to drive git bisect from a subdirectory and pass a > file name (or pathspec) that is relative to that subdirectory rather > than relative to the root of the worktree? Can `git bisect good` or > `git bisect bad` of later bisection steps be invoked from different > subdirectories or the root?
I think the answers are no and no. Entries in BISECT_NAMES and BISECT_LOG are not getting any prefix.
