From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Christian Couder <christian.couder@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Junio C Hamano <gitster@pobox.com>,
Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>,
louis--alexandre stuber
<louis--alexandre.stuber@ensimag.grenoble-inp.fr>,
Christian Couder <chriscool@tuxfamily.org>,
Thomas Nguy <thomasxnguy@gmail.com>,
Valentin Duperray <valentinduperray@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: [PATCH] bisect: revise manpage
Date: Fri, 26 Jun 2015 15:00:51 +0200 [thread overview]
Message-ID: <vpqmvzmwrng.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAP8UFD1GwH1ewapraL6cms04OVk8wHdtv+TJ7=HKL0_CLGjK-g@mail.gmail.com> (Christian Couder's message of "Fri, 26 Jun 2015 14:44:14 +0200")
Christian Couder <christian.couder@gmail.com> writes:
> On Fri, Jun 26, 2015 at 1:30 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>
> [...]
>
>> +Eventually there will be no more revisions left to bisect, and the
>> +command will print out a description of the first bad commit, and also
>> +create a reference called `refs/bisect/bad` that points at that
>> +commit.
>
> This could be understood as meaning that `refs/bisect/bad` is created
> only at the end of the bisection.
>
>> -Eventually there will be no more revisions left to bisect, and you
>> -will have been left with the first bad kernel revision in "refs/bisect/bad".
>
> The original looks better to me in this regard.
I'm changing it to:
Eventually there will be no more revisions left to bisect, and the
command will print out a description of the first bad commit. The
reference `refs/bisect/bad` created by bisect will point at that
commit.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-06-26 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:30 [PATCH] bisect: revise manpage Michael Haggerty
2015-06-26 12:44 ` Christian Couder
2015-06-26 13:00 ` Matthieu Moy [this message]
2015-06-26 13:15 ` Christian Couder
2015-06-26 14:58 ` Michael Haggerty
2015-06-26 15:28 ` Christian Couder
2015-06-26 16:30 ` Matthieu Moy
2015-06-26 17:47 ` Junio C Hamano
2015-06-26 20:22 ` [PATCH v10.1 3/7] Documentation/bisect: revise overall content Matthieu Moy
2015-06-26 12:50 ` [PATCH] bisect: revise manpage Matthieu Moy
2015-06-26 14:55 ` Michael Haggerty
2015-06-26 16:35 ` Matthieu Moy
2015-06-26 17:54 ` Junio C Hamano
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=vpqmvzmwrng.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=louis--alexandre.stuber@ensimag.grenoble-inp.fr \
--cc=mhagger@alum.mit.edu \
--cc=thomasxnguy@gmail.com \
--cc=valentinduperray@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.