git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Kevin Daudt <me@ikke.info>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] bisect: clarify that one can select multiple good commits
Date: Sat, 11 Nov 2017 08:46:26 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1711110846001.9944@localhost.localdomain> (raw)
In-Reply-To: <20171111134430.GA30635@alpha.vpn.ikke.info>

On Sat, 11 Nov 2017, Kevin Daudt wrote:

> On Sat, Nov 11, 2017 at 08:26:00AM -0500, Robert P. J. Day wrote:
> >
> > Current man page for "bisect" is inconsistent explaining the fact that
> > "git bisect" takes precisely one bad commit, but one or more good
> > commits, so tweak the man page in a few places to make that clear.
> >
> > rday
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> >
> > ---
> >
> >   i also exercised literary license to reword an example to look for a
> > commit where performance was *degraded* rather than improved, since i
> > think that's the sort of thing that people would be more interested
> > in.
> >
> >  In fact, `git bisect` can be used to find the commit that changed
> >  *any* property of your project; e.g., the commit that fixed a bug, or
> > -the commit that caused a benchmark's performance to improve. To
> > +the commit that caused a benchmark's performance to degrade. To
> >  support this more general usage, the terms "old" and "new" can be used
> >  in place of "good" and "bad", or you can choose your own terms. See
> >  section "Alternate terms" below for more information.
> > @@ -58,7 +58,7 @@ $ git bisect bad                 # Current version is bad
> >  $ git bisect good v2.6.13-rc2    # v2.6.13-rc2 is known to be good
> >  ------------------------------------------------
> >
>
> I think this example was meant to suggest that it's not only possible to
> find bad things (bugs, performance degradations), but also the opposite
> (when was a bug fixed, what caused the performance to change).
>
> So I think it's good to keep the example like it is.

  ok, anyone else have any strong opinions on the subject?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

      reply	other threads:[~2017-11-11 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 13:26 [PATCH] bisect: clarify that one can select multiple good commits Robert P. J. Day
2017-11-11 13:44 ` Kevin Daudt
2017-11-11 13:46   ` Robert P. J. Day [this message]

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=alpine.LFD.2.21.1711110846001.9944@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=git@vger.kernel.org \
    --cc=me@ikke.info \
    /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).