From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: Junio C Hamano <gitster@pobox•com>,
antoine.delaite@ensimag•grenoble-inp.fr,
louis--alexandre.stuber@ensimag•grenoble-inp.fr,
chriscool@tuxfamily•org, thomasxnguy@gmail•com,
valentinduperray@gmail•com, git@vger•kernel.org
Subject: Re: [PATCH] bisect: revise manpage
Date: Fri, 26 Jun 2015 14:50:16 +0200 [thread overview]
Message-ID: <vpqwpyqws53.fsf@anie.imag.fr> (raw)
In-Reply-To: <12a2e2d5e545459837b5eb2356cfc2fe4e3ef631.1435317576.git.mhagger@alum.mit.edu> (Michael Haggerty's message of "Fri, 26 Jun 2015 13:30:26 +0200")
Michael Haggerty <mhagger@alum•mit.edu> writes:
> * Remove the "Look for a fix instead of a regression in the code"
> example, as (1) it was in the "git bisect run" section, but it
> doesn't use that command, and (2) I think this usage is adequately
> explained in the "Alternate terms" section.
[...]
> -* Look for a fix instead of a regression in the code
> -+
> -------------
> -$ git bisect start
> -$ git bisect new HEAD # current commit is marked as new
> -$ git bisect old HEAD~10 # the tenth commit from now is marked as old
> -------------
> -+
> -Let's consider the last commit has a given property, and that we are looking
> -for the commit which introduced this property. For each commit the bisection
> -guide us to, we will test if the property is present. If it is we will mark
> -the commit as new with 'git bisect new', otherwise we will mark it as old.
> -At the end of the bisect session, the result will be the first new commit (e.g
> -the first one with the property).
I disagree with this one: it's in the example section, not bisect run.
The other explanations are nice, but never show the full sequence of
commands so I think an example to sum up does help.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-06-26 12:50 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
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 ` Matthieu Moy [this message]
2015-06-26 14:55 ` [PATCH] bisect: revise manpage 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=vpqwpyqws53.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=antoine.delaite@ensimag$(echo .)grenoble-inp.fr \
--cc=chriscool@tuxfamily$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=louis--alexandre.stuber@ensimag$(echo .)grenoble-inp.fr \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=thomasxnguy@gmail$(echo .)com \
--cc=valentinduperray@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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