From: Christian Couder <christian.couder@gmail.com>
Date: Fri, 26 Jun 2015 13:15:29 GMT
Subject: Re: [PATCH] bisect: revise manpage
Message-ID: <CAP8UFD3y3gBp6bdLHus4TNo3LSwWLLOOWgzRR+6Yqh-rg4ASRg@mail.gmail.com>
In-Reply-To: <vpqmvzmwrng.fsf@anie.imag.fr>

On Fri, Jun 26, 2015 at 3:00 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> 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.

For the last sentence I'd suggest:

The reference called `refs/bisect/bad` will point at that commit.