From: Christian Couder <chriscool@tuxfamily.org>
To: Junio Hamano <junkio@cox.net>, David Symonds <dsymonds@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH] Bisect: add "skip" to the short usage string.
Date: Tue, 30 Oct 2007 05:40:58 +0100 [thread overview]
Message-ID: <20071030054058.ecf79b4f.chriscool@tuxfamily.org> (raw)
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
git-bisect.sh | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
This is an alternative patch to the previous one
with the same name.
Here I put "skip" just after "bad" and "good" as
suggested by David Symonds, both in the short and
long usage string.
diff --git a/git-bisect.sh b/git-bisect.sh
index 180c6c2..b74f44d 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -1,12 +1,14 @@
#!/bin/sh
-USAGE='[start|bad|good|next|reset|visualize|replay|log|run]'
+USAGE='[start|bad|good|skip|next|reset|visualize|replay|log|run]'
LONG_USAGE='git bisect start [<bad> [<good>...]] [--] [<pathspec>...]
reset bisect state and start bisection.
git bisect bad [<rev>]
mark <rev> a known-bad revision.
git bisect good [<rev>...]
mark <rev>... known-good revisions.
+git bisect skip [<rev>...]
+ mark <rev>... untestable revisions.
git bisect next
find next bisection to test and check it out.
git bisect reset [<branch>]
@@ -17,8 +19,6 @@ git bisect replay <logfile>
replay bisection log.
git bisect log
show bisect log.
-git bisect skip [<rev>...]
- mark <rev>... untestable revisions.
git bisect run <cmd>...
use <cmd>... to automatically bisect.'
--
1.5.3.4.1405.g6c7bae
next reply other threads:[~2007-10-30 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 4:40 Christian Couder [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 4:31 [PATCH] Bisect: add "skip" to the short usage string Christian Couder
2007-10-29 4:35 ` David Symonds
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=20071030054058.ecf79b4f.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).