From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Pieter de Bie <pdebie@ai.rug.nl>,
Jakub Narebski <jnareb@gmail.com>,
Manoj Srivastava <srivasta@ieee.org>,
"Thomas Adam" <thomas.adam22@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: bisect: add a few "git bisect run" examples
Date: Tue, 06 May 2008 21:59:57 -0700 [thread overview]
Message-ID: <7vwsm6g14i.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080507062931.dd72d7e1.chriscool@tuxfamily.org> (Christian Couder's message of "Wed, 7 May 2008 06:29:31 +0200")
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.
next prev parent reply other threads:[~2008-05-07 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 4:29 [PATCH 2/2] Documentation: bisect: add a few "git bisect run" examples Christian Couder
2008-05-07 4:59 ` Junio C Hamano [this message]
2008-05-07 6:29 ` Matthieu Moy
2008-05-07 7:25 ` Miklos Vajna
2008-05-07 22:18 ` Christian Couder
2008-05-07 16:09 ` Jon Loeliger
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=7vwsm6g14i.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pdebie@ai.rug.nl \
--cc=srivasta@ieee.org \
--cc=thomas.adam22@gmail.com \
/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).