Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Git Mailing List <git@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>
Cc: Junio C Hamano <junkio@cox.net>
Subject: gitk problems: can't unset "idinlist(...)"
Date: Fri, 20 Jul 2007 16:05:54 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707201554540.27249@woody.linux-foundation.org> (raw)


Ok, color me stumped, but gitk is unhappy.

Ingo and Thomas have just announced that they  have a unified x86 tree for 
both i386/x86-64, so I did

	gitk arch/i386 arch/x86_64

to look at what has happened recently in the kernel in that area.

I get the gitk history view, but no actual diffs, and I get an application 
error window saying

	can't unset "idinlist(57d1c91fa6d9146b309b7511f6432dea2a24858b)": no such element in array
	can't unset "idinlist(57d1c91fa6d9146b309b7511f6432dea2a24858b)": no such element in array
	    while executing
	"unset idinlist($id)"
	    (procedure "layouttail" line 11)
	    invoked from within
	"layouttail"
	    (procedure "layoutmore" line 35)
	    invoked from within
	"layoutmore $tlimit $allread"
	    (procedure "chewcommits" line 9)
	    invoked from within
	"chewcommits 1"
	    ("eval" body line 1)
	    invoked from within
	"eval $script"
	    (procedure "dorunq" line 9)
	    invoked from within
	"dorunq"
	    ("after" script)

which really doesn't tell me much.

It doesn't seem to happen without path limiting, and it also doesn't seem 
to happen for all paths (doing "gitk drivers/scsi" doesn't show it), but 
somehow that "arch/i386" part seems to bring it out.

I'm not seeing anything interesting or special about that named commit, or 
anything else that would make gitk unhappy. But it is.

Current kernel tree. Anybody else has any ideas? Somebody who knows 
tcl/tk, and gitk?

			Linus

             reply	other threads:[~2007-07-20 23:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 23:05 Linus Torvalds [this message]
2007-07-21  5:09 ` gitk problems: can't unset "idinlist(...)" Jeff King
2007-07-21  5:53   ` Linus Torvalds
2007-07-21  5:56     ` Junio C Hamano
2007-07-21  5:59     ` Jeff King
2007-07-21  6:06       ` Jeff King
2007-07-21  6:11     ` Linus Torvalds
2007-07-21  6:18       ` Jeff King
2007-07-21  6:24         ` Jeff King
2007-07-21  6:47           ` Linus Torvalds
2007-07-21  6:54             ` Jeff King
2007-07-21  9:32             ` pointer to pointer (was: gitk problems: can't unset "idinlist(...)") David Kastrup
2007-07-21  9:44               ` pointer to pointer David Kastrup
2007-07-21  6:34         ` gitk problems: can't unset "idinlist(...)" Linus Torvalds
2007-07-21 11:42 ` 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=alpine.LFD.0.999.0707201554540.27249@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --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