From: Alejandro Riveira <ariveira@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] git bisect visualize crash
Date: Wed, 3 Dec 2008 11:20:29 +0000 (UTC) [thread overview]
Message-ID: <gh5q1t$qjn$1@ger.gmane.org> (raw)
i'm using ubuntu 8.10 and git bisect visualize is crashing.
Noticed when bisecting the kernel but it is easily reproducible
in git repository as of today
$ git bisect bad
$ git bisect good HEAD~20
$ git bisect visualize (03-12 12:16)
Error in startup script: can't read "notflag": no such variable
while executing
"expr {!$notflag}"
("--not" arm line 2)
invoked from within
"switch -glob -- $arg {
"-d" -
"--date-order" {
set vdatemode($n) 1
# remove from origargs in case we hit an unknown option
set origarg..."
(procedure "parseviewargs" line 21)
invoked from within
"parseviewargs $view $args"
(procedure "start_rev_list" line 27)
invoked from within
"start_rev_list $curview"
(procedure "getcommits" line 5)
invoked from within
"getcommits {}"
(file "/usr/local/bin/gitk" line 10897)
$ git --version
git version 1.6.1.rc1
$
next reply other threads:[~2008-12-03 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 11:20 Alejandro Riveira [this message]
2008-12-04 14:34 ` [PATCH] gitk: fix 'can't read "notflag"' Johannes Schindelin
2008-12-04 15:09 ` Johannes Schindelin
2008-12-04 15:59 ` Johannes Sixt
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='gh5q1t$qjn$1@ger.gmane.org' \
--to=ariveira@gmail.com \
--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).