Package: git-doc
Severity: normal
The description of the paths options to git-bisect looks like this:
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
the tree is involved in the problem you are tracking down, by giving
paths parameters when you say bisect start, like this:
$ git bisect start -- arch/i386 include/asm-i386
If you know beforehand more than one good commits, you can narrow the
bisect space down without doing the whole tree checkout every time you
...
Its unclear whether this tells git that the error definately *is* in arch/i386
include/asm-i386, or definately *isn't* in either of those paths. Also, the
newline after the indented line showing the shell is missing (the last two
lines quoted above describe the next bisect feature being discussed).
Stack overflow fixes it like this:
git bisect start -- arch/i386 include/asm-i386
Bisect will only consider commits that touch the folders specified.
In truth I think I'm looking at git 1.7.3.2 man pages but I guess its in the
old debian version as well and I find if I don't use reportbug I don't bother,
so I'm hoping the dev will just forward this to upstream since they are
used to doing that and don't have to figure out how for every blinking
different package thank you I love you debian.
-- System Information:
Debian Release: 5.0.9
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
