From: walt <w41ter@gmail.com>
To: git@vger.kernel.org
Subject: Is this a git-bisect bug?
Date: Sat, 21 Feb 2009 09:07:28 -0800 [thread overview]
Message-ID: <gnpccl$l69$1@ger.gmane.org> (raw)
I'm using the current git.git to bisect a bug in Linus.git.
I got this far and then ran into trouble:
good 2.6.29-rc5-00094-gc951aa6
bad 2.6.29-rc5-00112-g3501033
A glance at git log will show that those two commits were
both from Feb 17 with only one other commit between them.
So, why does this happen?:
$git bisect start 3501033 c951aa6
Bisecting: 8 revisions left to test after this
be716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption bug
git log shows that commit is from Jan 13, way back in 2.6.29-rc3.
Can anyone reproduce/explain this?
Thanks!
next reply other threads:[~2009-02-21 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 17:07 walt [this message]
2009-02-21 17:25 ` Is this a git-bisect bug? Teemu Likonen
2009-02-21 20:56 ` walt
2009-02-22 6:47 ` Christian Couder
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='gnpccl$l69$1@ger.gmane.org' \
--to=w41ter@gmail.com \
--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).