From: Olaf Hering <olh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git-bisect doesnt record bad commits
Date: Mon, 6 Feb 2006 23:24:48 +0100 [thread overview]
Message-ID: <20060206222448.GA9196@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0602061417510.3854@g5.osdl.org>
On Mon, Feb 06, Linus Torvalds wrote:
>
>
> 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").
Thats good enough for me to restore my steps, I think. Thanks.
--
short story of a lazy sysadmin:
alias appserv=wotan
prev parent reply other threads:[~2006-02-06 22:24 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
2006-02-06 22:24 ` Olaf Hering [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=20060206222448.GA9196@suse.de \
--to=olh@suse.de \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.