From: Johannes Sixt <j.sixt@viscovery.net>
To: "Andreas J. Koenig" <andreas.koenig.7os6VVqR@franz.ak.mind.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] Git bisect not finding the right commit
Date: Thu, 19 Jan 2012 09:23:01 +0100 [thread overview]
Message-ID: <4F17D2E5.7000400@viscovery.net> (raw)
In-Reply-To: <87r4yw8j4i.fsf@franz.ak.mind.de>
Am 1/19/2012 4:29, schrieb Andreas J. Koenig:
> - A -> B -> C - D ->
> \ /
> - E - F -
>
> A v5.15.5
> B v5.15.5-20-gfd76d40
> C v5.15.5-81-gcfe287a
> D v5.15.5-159-ga71d67b
> E v5.15.4-110-g27b29ec
> F v5.15.4-169-g3582575
I haven't looked at the actual history, but given the names of the commits
as produced by git-describe, I doubt that your history graph sketched
above is correct. Doesn't it look more like this:
A -- B -- C -- D --
/ /
-- X -- E -- F
where X is v5.15.4?
To find a commit between A and B, you must declare F as "good".
-- Hannes
prev parent reply other threads:[~2012-01-19 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 3:29 [BUG] Git bisect not finding the right commit Andreas J. Koenig
2012-01-19 8:20 ` Junio C Hamano
2012-01-20 7:56 ` Andreas J. Koenig
2012-01-20 18:09 ` Junio C Hamano
2012-01-24 20:21 ` Jeff King
2012-01-19 8:23 ` Johannes Sixt [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=4F17D2E5.7000400@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=andreas.koenig.7os6VVqR@franz.ak.mind.de \
--cc=git@vger.kernel.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).