From: "Han-Wen Nienhuys" <hanwenn@gmail.com>
To: git@vger.kernel.org
Subject: gitk bug
Date: Wed, 30 May 2007 20:31:20 -0300 [thread overview]
Message-ID: <f329bf540705301631q7906eb1dv9291fd088cd88282@mail.gmail.com> (raw)
git init
mkdir -p x/y/z
echo hoi > x/y/z/file1
echo hoi > x/y/z/file2
git add .
git commit -m 'start'
gitk
->
click "Tree". Open "x" directory.
Result:
can't read "treeheight(y/)": no such element in array
can't read "treeheight(y/)": no such element in array
(reading value of variable to increment)
invoked from within
"incr treeheight($x) $n"
(procedure "treeopendir" line 15)
invoked from within
"treeopendir $w $e"
(procedure "treeclick" line 20)
invoked from within
this is with
commit 322bcd9a9a2c0081c66414bde64e0d443c9ec922
Merge: a77a33a... 8558fd9...
Author: Junio C Hamano <junkio@cox.net>
Date: Tue May 29 01:24:20 2007 -0700
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next reply other threads:[~2007-05-30 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 23:31 Han-Wen Nienhuys [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-07 16:19 gitk bug php fan
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=f329bf540705301631q7906eb1dv9291fd088cd88282@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).