From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 07 May 2008 04:59:57 GMT
Subject: Re: [PATCH 2/2] Documentation: bisect: add a few "git bisect run" examples
Message-ID: <7vwsm6g14i.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080507062931.dd72d7e1.chriscool@tuxfamily.org>

Christian Couder <chriscool@tuxfamily.org> writes:

> Before this patch, there were no proper "git bisect run" example.

As if there were improper examples, and as if this patch adds a proper
one.  Drop "proper" and add sign-off perhaps?  ;-)

> ---
>  Documentation/git-bisect.txt |   26 ++++++++++++++++++++++++++
>  1 files changed, 26 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
> index 698ffde..a05963a 100644
> --- a/Documentation/git-bisect.txt
> +++ b/Documentation/git-bisect.txt
> @@ -224,6 +224,32 @@ tree to the pristine state.  Finally the "run" script can exit with
>  the status of the real test to let "git bisect run" command loop to
>  know the outcome.
>  
> +EXAMPLES
> +--------
> ...
> +* Automatically bisect a broken test case using a custom script:
> ++
> +------------
> +echo "#"\!"/bin/sh" > ~/test.sh
> +echo "make install || exit 125" >> ~/test.sh
> +echo "~/check_test_case.sh" >> ~/test.sh
> +chmod u+x ~/test.sh

s/install//; let's not set a bad example of installing first and then
testing.