From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: git-bisect failure
Date: Sat, 10 Sep 2005 14:13:43 -0700 [thread overview]
Message-ID: <20050910141343.578649c7.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509101202070.30958@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
> On Sat, 10 Sep 2005, Andrew Morton wrote:
> >
> > Junio C Hamano <junkio@cox.net> wrote:
> > >
> > > So it _might_
> > > be possible that you said "current LDT" was bad when it was
> > > actually good. That is one possible explanation.
> >
> > I agree. Mea culpa. Sorry.
>
> Well, this was actually something I hit when testign bisection too: it
> _is_ very unforgiving of mistakes.
Yes. That was my third attempt. You basically _have_ to write down the
good/bad sequence as you go. One slip and you've blown an hour's work.
> So the bisection algorithm may have done the right thing from a technical
> standpoint, but I suspect it could be made to be a bit more forgiving, or
> at least when somebody realizes that bisection didn't work right, we could
> have the trail of good/bad markings to try to debug what happened...
Yup. Simply keeping a little log file would suffice.
next prev parent reply other threads:[~2005-09-10 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 8:10 git-bisect failure Andrew Morton
2005-09-09 9:14 ` Junio C Hamano
2005-09-10 2:39 ` Junio C Hamano
2005-09-10 9:26 ` Andrew Morton
2005-09-10 19:07 ` Linus Torvalds
2005-09-10 21:13 ` Andrew Morton [this message]
2005-09-10 21:32 ` Linus Torvalds
2005-09-10 21:40 ` Junio C Hamano
2005-09-10 22:13 ` Junio C Hamano
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=20050910141343.578649c7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/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).