From: Michael <barra_cuda@katamail.com>
To: git@vger.kernel.org
Subject: gitk: error on find
Date: Tue, 21 Feb 2006 14:44:27 +0100 [thread overview]
Message-ID: <200602211444.27162.barra_cuda@katamail.com> (raw)
On GIT repository:
~/git$ git --version
git version 1.2.0
~/git$ gitk --all -d
if I search for "1.0.0" and hit "return", gitk gives:
error:
invalid command name "contmergediff"
invalid command name "contmergediff"
while executing
"contmergediff $ids"
(procedure "gettreediffline" line 14)
invoked from within
"gettreediffline file5 c894168631e4b7da66ed3993a4c92380d38599a8"
...and goes to commit 8d712aafd2df3c1f5147a28947f98cefe667cf76, while the
first commit containing "1.0.0" is c894168631e4b7da66ed3993a4c92380d38599a8
In general, pressing <return> instead of clicking "find", causes gitk to skip
a commit (without other errors). This behaviour is present since (at last)
GIT version 1.0.0.
Searching for "1.0.0" but clicking on "find" gives no errors.
I think "contmergediff" is an old procedure, but I don't know how to fix it
(nor exactly what was meant to do). The error was first introduced with
commit b77b02785d2f589ca336fc449ee1c27837263dac (it was a big change, so the
"contmergediff" line was probably forgotten).
reply other threads:[~2006-02-21 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200602211444.27162.barra_cuda@katamail.com \
--to=barra_cuda@katamail.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).