git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: git@vger.kernel.org
Subject: Re: [BUG] git-1.7.2-rc1, cherry-picking with gitk
Date: Fri, 09 Jul 2010 14:27:50 -0700	[thread overview]
Message-ID: <4C379456.9030401@gmail.com> (raw)
In-Reply-To: <4C3792E6.5060302@gmail.com>

On 09/07/10 14:21, Chris Packham wrote:
> Hi,
> 
> Just noticed this when I was trying to cherry-pick a commit from one
> branch to another.
> 
> I launch gitk with 'gitk master..work' and right-click a commit to be
> cherry-picked. The cherry-pick seems to work (i.e. a new commit appears
> on master) but I get the following message from gitk:
> 
> can't read "circleitem(5)": no such element in array
> can't read "circleitem(5)": no such element in array
>     while executing
> "$canv itemconf $circleitem($row) -fill $ofill"
>     (procedure "redrawtags" line 13)
>     invoked from within
> "redrawtags $oldhead"
>     (procedure "cherrypick" line 46)
>     invoked from within
> "cherrypick"
>     invoked from within
> ".rowctxmenu invoke active"
>     ("uplevel" body line 1)
>     invoked from within
> "uplevel #0 [list $w invoke active]"
>     (procedure "tk::MenuInvoke" line 50)
>     invoked from within
> "tk::MenuInvoke .rowctxmenu 1"
>     (command bound to event)
> 
> I've been doing similar things with older versions of git without
> problems (technically I usually do 'gitk --all' instead of 'gitk
> master..work').
> 
> --
> Thanks,
> Chris

Just following up if I use 'gitk --all' I don't see the problem. I tried
git 1.6.4.3 and saw the same error message with 'gitk master..work'

      reply	other threads:[~2010-07-09 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 21:21 [BUG] git-1.7.2-rc1, cherry-picking with gitk Chris Packham
2010-07-09 21:27 ` Chris Packham [this message]

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=4C379456.9030401@gmail.com \
    --to=judge.packham@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).