# [PATCH] rev-list documentation: add "--bisect-all".

2 messages from 2007-10-16 to 2007-10-16. Participants: Christian Couder, Ralf Wildenhues.
Thread: https://gitlist.dev/t/10299

## Christian Couder, 2007-10-16 03:59

Subject: [PATCH] rev-list documentation: add "--bisect-all".
Message-ID: <20071016055905.55c1d280.chriscool@tuxfamily.org>
URL: https://gitlist.dev/e/20071016055905.55c1d280.chriscool%40tuxfamily.org

```
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-rev-list.txt |   16 ++++++++++++++++
 1 files changed, 16 insertions(+), 0 deletions(-)

	Le lundi 15 octobre 2007, Frank Lichtenheld a écrit :
	>
	> --bisect-all is still missing a Documentation/ patch.

	Thanks for catching that. 
	Here is a patch.

diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
index 7cd0e89..f6dd0c4 100644
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -34,6 +34,7 @@ SYNOPSIS
 	     [ \--pretty | \--header ]
 	     [ \--bisect ]
 	     [ \--bisect-vars ]
+	     [ \--bisect-all ]
 	     [ \--merge ]
 	     [ \--reverse ]
 	     [ \--walk-reflogs ]
@@ -354,6 +355,21 @@ the expected number of commits to be tested if `bisect_rev`
 turns out to be bad to `bisect_bad`, and the number of commits
 we are bisecting right now to `bisect_all`.
 
+--bisect-all::
+
+This outputs all the commit objects between the included and excluded
+commits, ordered by their distance to the included and excluded
+commits. The farthest from them is displayed first. (This is the only
+one displayed by `--bisect`.)
+
+This is usefull because it makes it easy to choose a good commit to
+test when you want to avoid to test some of them for some reason (they
+may not compile for example).
+
+This option can be used along with `--bisect-vars`, in this case,
+after all the sorted commit objects, there will be the same text as if
+`--bisect-vars` has been used alone.
+
 --
 
 Commit Ordering
-- 
1.5.3.4.213.g68ad5

```

## Ralf Wildenhues, 2007-10-16 10:42

Subject: Re: [PATCH] rev-list documentation: add "--bisect-all".
Message-ID: <20071016104257.GB1170@ins.uni-bonn.de>
URL: https://gitlist.dev/e/20071016104257.GB1170%40ins.uni-bonn.de
In-Reply-To: <20071016055905.55c1d280.chriscool@tuxfamily.org>

```
Hello,

A couple of typos:

* Christian Couder wrote on Tue, Oct 16, 2007 at 05:59:05AM CEST:
> 
> diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
> index 7cd0e89..f6dd0c4 100644
> --- a/Documentation/git-rev-list.txt
> +++ b/Documentation/git-rev-list.txt
[...]
> @@ -354,6 +355,21 @@ the expected number of commits to be tested if `bisect_rev`
>  turns out to be bad to `bisect_bad`, and the number of commits
>  we are bisecting right now to `bisect_all`.
>  
> +--bisect-all::
> +
> +This outputs all the commit objects between the included and excluded
> +commits, ordered by their distance to the included and excluded
> +commits. The farthest from them is displayed first. (This is the only
> +one displayed by `--bisect`.)
> +
> +This is usefull because it makes it easy to choose a good commit to

s/usefull/useful/

> +test when you want to avoid to test some of them for some reason (they
> +may not compile for example).
> +
> +This option can be used along with `--bisect-vars`, in this case,
> +after all the sorted commit objects, there will be the same text as if
> +`--bisect-vars` has been used alone.

s/has/had/

Cheers,
Ralf

```