From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Bisection visualization hint..
Date: Tue, 30 Aug 2005 14:03:37 -0400 [thread overview]
Message-ID: <43149F79.4020809@gmail.com> (raw)
In-Reply-To: <7vhdd7joz6.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Linus Torvalds <torvalds@osdl.org> writes:
>
>>I'm testing bisection to find a bug that causes my G5 to no longer boot,
>>and during the process have found this command line very nice:
>>
>> gitk bisect/bad --not $(cd .git/refs ; ls bisect/good-*)
>>
>>it basically shows the state of bisection with the known bad commit as the
>>top, and cutting off all the good commits - so what you see are the
>>potential buggy commits.
>
>>But it's not the nicest of command lines and depends on knowing how
>>bisection works, so maybe we could make
>>
>> git bisect visualize
>>
>>do this for us?
>
> Will do.
>
> Another thing that might make sense is roll it also into gitk, a
> new command from "File" menu to cause it to re-read not just ref
> values but the rev-list itself out of that particular rev-list
> command (and add any other common patterns as we discover them).
Unless gitk will always be part of git, this is better off as a gitk
feature or gitk helper script. IE. it belongs in the gitk namespace, not
the git namespace.
That said, a wrapper for "git show-branch" (git show-bisect?) would be
nice also.
next prev parent reply other threads:[~2005-08-30 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 17:29 Bisection visualization hint Linus Torvalds
2005-08-30 17:47 ` Junio C Hamano
2005-08-30 18:03 ` A Large Angry SCM [this message]
2005-08-30 18:17 ` Linus Torvalds
2005-08-30 18:04 ` Fix bisection terminating condition Linus Torvalds
2005-08-30 18:56 ` Junio C Hamano
2005-08-30 18:22 ` [PATCH] 'git bisect visualize' Junio C Hamano
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=43149F79.4020809@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.