From: Linus Torvalds <torvalds@osdl.org>
To: Olaf Hering <olh@suse.de>
Cc: git@vger.kernel.org
Subject: Re: git-bisect doesnt record bad commits
Date: Mon, 6 Feb 2006 14:21:12 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602061417510.3854@g5.osdl.org> (raw)
In-Reply-To: <20060206215442.GA12209@suse.de>
On Mon, 6 Feb 2006, Olaf Hering wrote:
>
> Is there a reason why git-bisect does only record good ones? I would
> really like to know which commits did crash for me. :(
It does. Look in the bisection log (".git/BISECT_LOG").
Now, the reason it doesn't actually save them away as _tags_ is because
technically, it doesn't need to. The algorithm itself only really cares
about the most recently marked-bad commit, and the others are totally
uninteresting from an algorithmic standpoint.
That said, if you want the visualization tools (for example) to show them,
you could certainly _create_ the tags, if you want to. The fact that they
wouldn't be used by the bisection algorithm doesn't mean that you can't
create the ".git/refs/bisect/bad-<sha1>" file in _addition_ to the one
that marks the latest one.
Linus
next prev parent reply other threads:[~2006-02-06 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 21:54 git-bisect doesnt record bad commits Olaf Hering
2006-02-06 22:21 ` Linus Torvalds [this message]
2006-02-06 22:24 ` Olaf Hering
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.0602061417510.3854@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=olh@suse.de \
/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).