git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Paul Mackerras <paulus@samba.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk: git bisect view doesn't work
Date: Mon, 01 Dec 2008 17:29:53 +0100	[thread overview]
Message-ID: <49341101.8050400@viscovery.net> (raw)
In-Reply-To: <4933F819.1010701@viscovery.net>

Johannes Sixt schrieb:
> gitk bails out like this if I do "git bisect view":
> 
> $ git bisect start HEAD HEAD~2
> Bisecting: 0 revisions left to test after this
> [9a61060c7e0d112d0742f5b845210ea8c41b6c6b] Added encoding
> 
> $ git bisect view
> 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)

Bisection points to this commit:

commit 2958228430b63f2e38c55519d1f98d8d6d9e23f3
Author: Paul Mackerras <paulus@samba.org>
Date:   Tue Nov 18 19:44:20 2008 +1100

    gitk: Fix switch statement in parseviewargs

-- Hannes

  reply	other threads:[~2008-12-01 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 14:43 gitk: git bisect view doesn't work Johannes Sixt
2008-12-01 16:29 ` Johannes Sixt [this message]
2008-12-01 17:25   ` [PATCH (GITK FIX)] gitk: Fix the "notflag: no such variable" error in --not processing Alexander Gavrilov
2008-12-01 22:45     ` Paul Mackerras

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=49341101.8050400@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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).