From: Johannes Sixt <j.sixt@viscovery.net>
To: Chris Clayton <chris2553@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Problem with git bisect in git-1.6.3.3
Date: Thu, 09 Jul 2009 08:39:31 +0200 [thread overview]
Message-ID: <4A5590A3.8070404@viscovery.net> (raw)
In-Reply-To: <c6b1100b0907082242y7b348b13m8a4607c96b1d164b@mail.gmail.com>
Chris Clayton schrieb:
> git bisect start
> # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30
> git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6
> # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2
...
> but, from Makefile, it appears the last "bad" has placed me at a
> change earlier than 2.6.30:
>
> [chris:~/kernel/linux-2.6]$ head Makefile
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 30
> EXTRAVERSION = -rc6
...
> I'm not an experienced git user, so it may be that I have made an
> error or false assumption.
Not an error, but false assumptions:
http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977
Just continue bisecting. If you can't test the version that bisect warps
you to because the feature where the bug happens is not present, mark that
revision as "good".
-- Hannes
next prev parent reply other threads:[~2009-07-09 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 5:42 Problem with git bisect in git-1.6.3.3 Chris Clayton
2009-07-09 6:39 ` Johannes Sixt [this message]
2009-07-09 7:13 ` Chris Clayton
2009-07-10 5:05 ` 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=4A5590A3.8070404@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=chris2553@googlemail.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).