Re: Article about "git bisect run" on LWN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le samedi 7 février 2009, David Symonds a écrit :
> On Sat, Feb 7, 2009 at 3:41 PM, Christian Couder
>
> <chriscool@xxxxxxxxxxxxx> wrote:
> > It might be useful to have a list of always good commits too, and use
> > it like this:
> >
> > $ git bisect start <bad> <good> $(cat always_good.txt)
> > $ git bisect skip $(cat always_skipped.txt)
> > $ git bisect run ./my_test_script.sh
>
> Your test script could just do this at its start instead:
>
>   if cat always_good.txt | grep $(rev-parse HEAD); then
>     exit 0

This won't work, because when you give one good rev, you say that all the 
ancestors of this rev are good (not just that the rev you give is good).

>   elif cat always_skipped.txt | grep $(rev-parse HEAD); then
>     exit 125
>   fi

If you have a range like v1..v2 in "always_skipped.txt" this won't work.
And anyway it may be less efficient because it may perform many useless 
checkouts.

Regards,
Christian.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux