From: walter harms <wharms@bfs•de>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: git@vger•kernel.org
Subject: Re: help: bisect single file from repos
Date: Mon, 07 Dec 2009 17:05:10 +0100 [thread overview]
Message-ID: <4B1D27B6.7010900@bfs.de> (raw)
In-Reply-To: <4B1D1A5A.9060004@drmicha.warpmail.net>
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.
i already had the hint that i need to do:
git bisect start bad_commit_id good_commit_id -- ash.c
Ntl, there is one more question, how can i make sure that
i use the right version ? first i toughed that cherry-pick is the right idea
but it seems that that will apply onyl certain patches ?
re,
wh
next prev parent reply other threads:[~2009-12-07 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 12:59 help: bisect single file from repos walter harms
2009-12-07 15:08 ` Michael J Gruber
2009-12-07 16:05 ` walter harms [this message]
2009-12-08 8:17 ` Christian Couder
2009-12-08 13:41 ` walter harms
2009-12-08 18:35 ` Junio C Hamano
2009-12-09 1:28 ` SZEDER Gábor
2009-12-09 8:27 ` Nanako Shiraishi
2009-12-09 9:45 ` SZEDER Gábor
2009-12-09 12:12 ` walter harms
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=4B1D27B6.7010900@bfs.de \
--to=wharms@bfs$(echo .)de \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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