From: Linus Torvalds <torvalds@osdl.org>
To: linux@horizon.com
Cc: paul@permanentmail.com, git@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Bisects that are neither good nor bad
Date: Mon, 29 May 2006 17:46:32 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605291744390.5623@g5.osdl.org> (raw)
In-Reply-To: <20060529225632.7073.qmail@science.horizon.com>
On Mon, 29 May 2006, linux@horizon.com wrote:
>
> It's also worth repeating some advice from the manual:
>
> >> 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
I'm not 100% sure this works - I think it has problems with the ending
condition because there always ends up being more commits in between when
the commit space isn't dense, so the "no commits left" thing doesn't
trigger. But "git bisect visualize" should hopefully help make it obvious
Linus
prev parent reply other threads:[~2006-05-30 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 22:56 Bisects that are neither good nor bad linux
2006-05-30 0:46 ` Linus Torvalds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0605291744390.5623@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=paul@permanentmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).