From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: totally confused as to what "git bisect skip" is supposed to do
Date: Fri, 9 Feb 2018 14:51:51 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1802091447540.14489@localhost.localdomain> (raw)
In-Reply-To: <xmqqo9kyvthx.fsf@gitster-ct.c.googlers.com>
On Fri, 9 Feb 2018, Junio C Hamano wrote:
> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
> > i'm confused ... why, after skipping a good chunk in the
> > interval [v4.13,v4.14], do i still have exactly 7300 revisions to
> > bisect? what am i so hopelessly misunderstanding here?
>
> Are you really "skipping" a chunk in the interval?
i don't know ... am i? how should i interpret the man page?
> I thought that "git bisect skip" is a way for you to respond, when
> "git bisect" gave you a commit to test, saying "sorry, I cannot test
> that exact version, please offer me something else to test". And
> each time you say that, you are not narrowing the search space in
> any way, so it is understandable that the number of candidate bad
> commits will not decrease.
i caught that part of the man page, but i'm trying to understand
what i'm reading here:
https://blog.smart.ly/2015/02/03/git-bisect-debugging-with-feature-branches/
particularly this suggestion:
$ git bisect start master 75369f4a4c026772242368d870872562a3b693cb
$ for rev in $(git rev-list
75369f4a4c026772242368d870872562a3b693cb..master --merges
--first-parent); do
> git rev-list $rev^2 --not $rev^
> done | xargs git bisect skip
my interpretation of that page is how, after starting a bisection, one
can use "git bisect skip" to explicitly disqualify a sizable number of
commits from consideration, speeding up the subsequent bisection.
if that's not what that web page is describing, then what *is* it
talking about?
rday
next prev parent reply other threads:[~2018-02-09 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 19:36 totally confused as to what "git bisect skip" is supposed to do Robert P. J. Day
2018-02-09 19:43 ` Junio C Hamano
2018-02-09 19:51 ` Robert P. J. Day [this message]
2018-02-12 10:44 ` Robert P. J. Day
2018-02-12 16:21 ` Christian Couder
2018-02-13 12:28 ` Robert P. J. Day
2018-02-13 12:59 ` Christian Couder
2018-02-13 13:10 ` Robert P. J. Day
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
List information: http://vger.kernel.org/majordomo-info.html
* 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.1802091447540.14489@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).