From: Michael Haggerty <mhagger@alum.mit.edu>
To: Christian Couder <christian.couder@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: 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 16:58:47 +0200 [thread overview]
Message-ID: <558D68A7.6010608@alum.mit.edu> (raw)
In-Reply-To: <CAP8UFD3y3gBp6bdLHus4TNo3LSwWLLOOWgzRR+6Yqh-rg4ASRg@mail.gmail.com>
On 06/26/2015 03:15 PM, Christian Couder wrote:
> 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.
I agree that is better.
> For the last sentence I'd suggest:
>
> The reference called `refs/bisect/bad` will point at that commit.
Or maybe
The reference `refs/bisect/bad` will be left pointing at that commit.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
next prev parent reply other threads:[~2015-06-26 14:59 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
2015-06-26 13:15 ` Christian Couder
2015-06-26 14:58 ` Michael Haggerty [this message]
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=558D68A7.6010608@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=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=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 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 NNTP newsgroup(s).