From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: should "git bisect" support "git bisect next?"
Date: Sat, 11 Nov 2017 06:42:53 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1711110639120.5632@localhost.localdomain> (raw)
the man page for "git bisect" makes no mention of "git bisect next",
but the script git-bisect.sh does:
#!/bin/sh
USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|replay|log|run]'
^^^^
LONG_USAGE='git bisect help
print this long help message.
git bisect start [--term-{old,good}=<term> --term-{new,bad}=<term>]
[--no-checkout] [<bad> [<good>...]] [--] [<pathspec>...]
reset bisect state and start bisection.
git bisect (bad|new) [<rev>]
mark <rev> a known-bad revision/
a revision after change in a given property.
git bisect (good|old) [<rev>...]
mark <rev>... known-good revisions/
revisions before change in a given property.
git bisect terms [--term-good | --term-bad]
show the terms used for old and new commits (default: bad, good)
git bisect skip [(<rev>|<range>)...]
mark <rev>... untestable revisions.
git bisect next
find next bisection to test and check it out.
... snip ...
case "$#" in
0)
usage ;;
*)
cmd="$1"
get_terms
shift
case "$cmd" in
help)
git bisect -h ;;
start)
bisect_start "$@" ;;
bad|good|new|old|"$TERM_BAD"|"$TERM_GOOD")
bisect_state "$cmd" "$@" ;;
skip)
bisect_skip "$@" ;;
next)
# Not sure we want "next" at the UI level anymore.
bisect_next "$@" ;;
... snip ...
so, is it supported or not? should be consistent.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2017-11-11 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 11:42 Robert P. J. Day [this message]
2017-11-11 14:07 ` should "git bisect" support "git bisect next?" Christian Couder
2017-11-11 14:38 ` Junio C Hamano
2017-11-11 19:46 ` Theodore Ts'o
2017-11-12 1:43 ` Junio C Hamano
2017-11-12 14:21 ` Christian Couder
2017-11-12 18:42 ` Theodore Ts'o
2017-11-13 1:40 ` Junio C Hamano
2017-11-12 9:17 ` Robert P. J. Day
2017-11-12 9:56 ` Junio C Hamano
2017-11-12 20:08 ` Stephan Beyer
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.1711110639120.5632@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).