From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio Hamano <junkio@cox.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Frank Lichtenheld <frank@lichtenheld.de>,
git@vger.kernel.org
Subject: Re: [PATCH] rev-list documentation: add "--bisect-all".
Date: Tue, 16 Oct 2007 12:42:57 +0200 [thread overview]
Message-ID: <20071016104257.GB1170@ins.uni-bonn.de> (raw)
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
next prev parent reply other threads:[~2007-10-16 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 3:59 [PATCH] rev-list documentation: add "--bisect-all" Christian Couder
2007-10-16 10:42 ` Ralf Wildenhues [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-17 6:05 Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016104257.GB1170@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).