From: Junio C Hamano <gitster@pobox.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org
Subject: Re: git-bisect feature suggestion: "git-bisect diff"
Date: Fri, 07 Dec 2007 01:58:35 -0800 [thread overview]
Message-ID: <7v63za4yic.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071207093439.GA21896@elte.hu> (Ingo Molnar's message of "Fri, 7 Dec 2007 10:34:39 +0100")
Ingo Molnar <mingo@elte.hu> writes:
> would be nice to have:
>
> git-bisect diff
>
> that enables one to have a look at the currently open bisection window,
> in git-log -p format. This would often be much faster to analyze than
> looking at git-bisect visualize. (and it could also be used in non-GUI
> workflows)
Hmm. It is very unfortunate that "bisect log" is taken for something
unrelated, so tentatively let's call it lumber.
$ git bisect lumber [-p] [--stat]
would give you the short-hand, hopefully.
---
git-bisect.sh | 12 +++++++++++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/git-bisect.sh b/git-bisect.sh
index 7a6521e..ee26624 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -1,6 +1,6 @@
#!/bin/sh
-USAGE='[start|bad|good|skip|next|reset|visualize|replay|log|run]'
+USAGE='[start|bad|good|skip|next|reset|visualize|log|replay|lumber|run]'
LONG_USAGE='git bisect start [<bad> [<good>...]] [--] [<pathspec>...]
reset bisect state and start bisection.
git bisect bad [<rev>]
@@ -15,6 +15,8 @@ git bisect reset [<branch>]
finish bisection search and go back to branch.
git bisect visualize
show bisect status in gitk.
+git bisect lumber
+ show bisect status in git log.
git bisect replay <logfile>
replay bisection log.
git bisect log
@@ -328,6 +330,12 @@ bisect_visualize() {
eval gitk refs/bisect/bad --not $not -- $(cat "$GIT_DIR/BISECT_NAMES")
}
+bisect_lumber() {
+ bisect_next_check fail
+ not=$(git for-each-ref --format='%(refname)' "refs/bisect/good-*")
+ eval git log "$@" refs/bisect/bad --not $not -- $(cat "$GIT_DIR/BISECT_NAMES")
+}
+
bisect_reset() {
test -f "$GIT_DIR/BISECT_NAMES" || {
echo "We are not bisecting."
@@ -451,6 +459,8 @@ case "$#" in
bisect_next "$@" ;;
visualize)
bisect_visualize "$@" ;;
+ lumber)
+ bisect_lumber "$@" ;;
reset)
bisect_reset "$@" ;;
replay)
next prev parent reply other threads:[~2007-12-07 9:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 9:34 git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-07 9:58 ` Junio C Hamano [this message]
2007-12-07 10:25 ` Junio C Hamano
2007-12-07 11:21 ` Ingo Molnar
2007-12-07 19:28 ` Junio C Hamano
2007-12-07 19:46 ` Ingo Molnar
2007-12-07 21:34 ` Jeff King
2007-12-07 21:35 ` Jeff King
2007-12-07 21:44 ` Junio C Hamano
2007-12-07 21:55 ` Jeff King
2007-12-07 22:03 ` Junio C Hamano
2007-12-07 22:07 ` Jeff King
2007-12-08 2:54 ` Junio C Hamano
2007-12-08 5:36 ` Christian Couder
2007-12-08 15:29 ` Ingo Molnar
2007-12-09 5:33 ` git-bisect run make -j64 kernel/ (was Re: git-bisect feature suggestion: "git-bisect diff") Christian Couder
2007-12-12 9:43 ` Ingo Molnar
2007-12-11 9:24 ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-11 9:29 ` Pierre Habouzit
2007-12-11 10:13 ` Jakub Narebski
2007-12-11 11:59 ` Pierre Habouzit
2007-12-11 12:25 ` Jeff King
2007-12-11 12:33 ` Jeff King
2007-12-11 14:05 ` Ingo Molnar
2007-12-11 14:43 ` [PATCH] Invert numbers and names in the git-shortlog summary mode Pierre Habouzit
2007-12-11 14:57 ` Ingo Molnar
2007-12-11 15:24 ` Pierre Habouzit
2007-12-11 15:34 ` Nicolas Pitre
2007-12-11 18:09 ` Junio C Hamano
2007-12-11 15:48 ` Ingo Molnar
2007-12-11 16:07 ` Pierre Habouzit
2007-12-11 16:11 ` Pierre Habouzit
2007-12-11 21:13 ` Ingo Molnar
2007-12-11 22:21 ` Junio C Hamano
2007-12-11 17:58 ` Junio C Hamano
2007-12-11 10:17 ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:22 しらいしななこ
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=7v63za4yic.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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).