Re: [PATCH] Documentation: More examples for git bisect
- From
Christian Couder <chriscool@tuxfamily.org>
- Date
- Mar 6, 2009, 20:08 UTC
- Message-ID
- <200903062108.09758.chriscool@tuxfamily.org>
- In-Reply-To
- <1236332255-15712-1-git-send-email-johnflux@gmail.com>
Le vendredi 6 mars 2009, John Tapsell a écrit :
Show 28 quoted lines
> Including passing parameters to the programs, and running more > complicated checks without requiring a seperate shell script. > > Signed-off-by: John Tapsell <johnflux@gmail.com> > --- > Documentation/git-bisect.txt | 27 ++++++++++++++++++++++++++- > 1 files changed, 26 insertions(+), 1 deletions(-) > > diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt > index 147ea38..7b8cfdd 100644 > --- a/Documentation/git-bisect.txt > +++ b/Documentation/git-bisect.txt > @@ -212,7 +212,7 @@ If you have a script that can tell if the current > source code is good or bad, you can automatically bisect using: > > ------------ > -$ git bisect run my_script > +$ git bisect run my_script arguments > ------------ > > Note that the "run" script (`my_script` in the above example) should > @@ -251,6 +251,22 @@ EXAMPLES > $ git bisect start HEAD v1.2 -- # HEAD is bad, v1.2 is good > $ git bisect run make # "make" builds the app > ------------ > ++ > +This looks for the first revision that fails to build between HEAD and > +the tag 'v1.2'.
There are a few trailing spaces in the above line but otherwise the patch looks good to me.
Acked-by: Christian Couder <chriscool@tuxfamily.org>
By the way, it would be nice if you could put me in CC.
Thanks, Christian.