public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: <linux-kernel@vger.kernel.org>
Subject: Alternative to 'git bisect visualize'?
Date: Mon, 9 Apr 2007 17:10:23 -0400	[thread overview]
Message-ID: <04fe01c77aeb$7d3cd370$294b82ce@stuartm> (raw)

The git mailing list seems to be git-dev, and I can't find a git-users
list anywhere. If there's somewhere better to ask this, please point
me in the right direction.

I've been learning git over the last few days. Specifically, I'm
trying out git bisect to locate a change between 2.6.17 and 2.6.18
that broke something.

I've reached a point where the kernel I build does not boot. Linus
says
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
"you should try to find another commit close-by". Other docs I've read
imply this is done with git bisect visualize.

My problem is that I don't have wish/tk installed. Is there a
text-based alternative to visualize that I can use? Or is there a
different method to locate a nearby commit?

The answer may involve something as simple as looking at some git
state; I am a git newbie, and reading the docs hasn't helped any, so I
won't be surprised to find out I'm overlooking something really
obvious.

Thanks in advance for any and all help,
..Stu


             reply	other threads:[~2007-04-09 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 21:10 Stuart MacDonald [this message]
2007-04-10  8:03 ` Alternative to 'git bisect visualize'? Paolo Ornati
2007-04-10 19:45   ` Stuart MacDonald
2007-04-10 20:00     ` Randy Dunlap
2007-04-10 20:04       ` Stuart MacDonald

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='04fe01c77aeb$7d3cd370$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=linux-kernel@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