From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: totally confused as to what "git bisect skip" is supposed to do
Date: Fri, 9 Feb 2018 14:36:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1802091431360.10982@localhost.localdomain> (raw)
all right, i'm sure i'm just being an idiot, but i always thought i
knew what "git bisect skip" did and, now that i'm trying to put
together a simple example, i'm utterly confused so here's a stripped
down example.
with linus kernel source code, start bisecting [v4.13,v4.14]:
$ git bisect start v4.14 v4.13
Bisecting: 7300 revisions left to test after this (roughly 13 steps)
[15d8ffc96464f6571ecf22043c45fad659f11bdd] Merge tag 'mmc-v4.14' of
git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
$
now, based on how linux kernel release candidates work, i want to
skip a sizable chunk of those revisions:
$ git bisect skip v4.14-rc1..v4.14-rc2
Bisecting: 7300 revisions left to test after this (roughly 13 steps)
[15d8ffc96464f6571ecf22043c45fad659f11bdd] Merge tag 'mmc-v4.14' of
git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
$
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?
rday
next reply other threads:[~2018-02-09 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 19:36 Robert P. J. Day [this message]
2018-02-09 19:43 ` totally confused as to what "git bisect skip" is supposed to do Junio C Hamano
2018-02-09 19:51 ` Robert P. J. Day
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
* 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.1802091431360.10982@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
/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).