Re: help: bisect single file from repos

From: Christian Couder <chriscool@tuxfamily.org>
Date: Dec 8, 2009, 08:17 UTC
Message-ID: <200912080917.17220.chriscool@tuxfamily.org>
In-Reply-To: <4B1D27B6.7010900@bfs.de>

Hi,

On lundi 07 décembre 2009, walter harms wrote:

Show 24 quoted lines

> Michael J Gruber schrieb:
> > walter harms venit, vidit, dixit 07.12.2009 13:59:
> >> Hi list,
> >> i am new to git (using: git version 1.6.0.2).
> >
> > though your git is not that new ;)
> >
> >> I would like to bisect a single file but i have only commit id, no
> >> tags.
> >>
> >> Background:
> >> I have a copy of the busybox git repos, and i know there is (perhaps)
> >> a bug in ash.c.
> >>
> >> how can i do that ?
> >
> > You don't need any tags for bisecting. The man page of git-bisect has
> > several examples on how to use it. Do you have a test script which
> > exposes the bug?
>
> unfortunately no, the error shows up very nicely when booting my
> embdedded system but not else (this is the reason i would to bisect that
> file only and not busybox completely). And from the man pages i got the
> impression that it is only possible the start with a tag.

The man page says:

git bisect start [<bad> [<good>...]] [--] [<paths>...]

and then:

"This command uses git rev-list --bisect to help drive the binary search process to find which change introduced a bug, given an old "good" commit object name and a later "bad" commit object name."

> i already had the hint that i need to do:
> git bisect start bad_commit_id good_commit_id -- ash.c

So did you try that?

> Ntl, there is one more question, how can i make sure that
> i use the right version ?

If you mean the right git version, then I think any 1.6.X should be enough.

> first i toughed  that cherry-pick is the right 
> idea but it seems that that will apply onyl certain patches ?

If you want to find the commit that introduced a bug, then you should not need cherry-pick.

Regards, Christian.