From: Sergey Vlasov <vsu@altlinux.ru>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: gitk merge display bugs (was: Re: Display of merges in gitk)
Date: Sat, 30 Jul 2005 18:32:33 +0400 [thread overview]
Message-ID: <20050730183233.572939be.vsu@altlinux.ru> (raw)
In-Reply-To: <17130.56620.137642.941175@cargo.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
On Fri, 29 Jul 2005 20:51:40 -0500 Paul Mackerras wrote:
> I have reworked the way gitk displays merges.
I have found a reproducible bug in gitk which seems to be in that new
code for merges. Run
gitk f4b3a4c30b5ea3a5de2a2597a3c53266017d02ba
on the git or cogito repository (that commit is from 2005-07-05), then
click the topmost commit ("Merge with Linus' current tree"), then click
it again - you get an error popup with this trace:
can't read "filelines(f13bbe7f56e49a11f6bfc3b73a463c741f969c9c,0,137)": no such element in array
can't read "filelines(f13bbe7f56e49a11f6bfc3b73a463c741f969c9c,0,137)": no such element in array
while executing
"$ctext insert end "-$filelines($p,$f,$ol)\n" m$pnum"
(procedure "processgroup" line 143)
invoked from within
"processgroup"
(procedure "processhunks" line 47)
invoked from within
"processhunks"
(procedure "getmergediffline" line 81)
invoked from within
"getmergediffline file10 {f4b3a4c30b5ea3a5de2a2597a3c53266017d02ba f13bbe7f56e49a11f6bfc3b73a463c741f969c9c} f4b3a4c30b5ea3a5de2a2597a3c53266017d02ba"
Another badness which appears with the same repository: run
gitk f13bbe7f56e49a11f6bfc3b73a463c741f969c9c
then repeated clicks on the topmost commit result in a different diff
shown (no error popups, however).
Also if I quickly move between commits, sometimes I get error popups
like:
can't unset "treepending": no such variable
while executing
"unset treepending"
(procedure "gettreediffline" line 9)
invoked from within
"gettreediffline file30 {429a9358763dfb98cd063e40dc49cbc049e2a268 154d3d2dd2656c23ea04e9d1c6dd4e576a7af6de}"
This error does not happen again if the same commit is selected.
All this happens both with current cogito
(134b78a167b5f77725cd8435849de7298b6de477) and git
(9e44f8980b8f41fbeea0a68035865e5778e4dc7d).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-30 14:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 1:51 Display of merges in gitk Paul Mackerras
2005-07-30 4:25 ` Junio C Hamano
2005-07-30 21:36 ` Shipping gitk as part of core git Junio C Hamano
2005-07-31 12:00 ` Paul Mackerras
2005-07-31 18:48 ` Junio C Hamano
2005-07-30 14:32 ` Sergey Vlasov [this message]
2005-08-05 14:10 ` Display of merges in gitk Linus Torvalds
2005-08-05 14:37 ` gitk "hyperlinks" (was Re: Display of merges in gitk) Linus Torvalds
2005-08-05 18:51 ` jepler
2005-08-06 3:36 ` Kay Sievers
2005-08-06 15:44 ` Linus Torvalds
2005-08-07 5:51 ` Kay Sievers
2005-08-06 18:27 ` gitweb "tag" display Junio C Hamano
2005-08-06 18:49 ` Junio C Hamano
2005-08-19 23:21 ` Paul Mackerras
2005-08-19 23:43 ` Johannes Schindelin
2005-08-20 19:09 ` Junio C Hamano
2005-08-07 5:50 ` Kay Sievers
2005-08-06 13:16 ` gitk "hyperlinks" (was Re: Display of merges in gitk) Paul Mackerras
2005-08-06 16:20 ` Linus Torvalds
2005-08-06 17:07 ` jepler
2005-08-06 17:59 ` gitk SHA link hovers Linus Torvalds
2005-08-07 12:04 ` Paul Mackerras
2005-08-06 16:31 ` gitk "hyperlinks" Junio C Hamano
2005-08-07 12:05 ` 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=20050730183233.572939be.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--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).