From: Stefan Haller <firstname.lastname@example.org>
To: Paul Mackerras <email@example.com>
Cc: Johannes Sixt <firstname.lastname@example.org>, email@example.com
Subject: Re: [BUG] gitk: clicking on a connecting line produces can't read "cflist_top"
Date: Thu, 4 Oct 2012 22:50:15 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Sorry, I didn't realize that there is a display mode where the
list of files is empty, not even showing a "Comments" entry.
Here's a patch that fixes it, plus another patch that is only related
in so far as the bug that it fixes was introduced by the same commit.
[PATCH 1/2] gitk: Fix error message when clicking on a connecting line
[PATCH 2/2] gitk: When searching, only highlight files when in Patch mode
next prev parent reply other threads:[~2012-10-04 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 8:40 [BUG] gitk: clicking on a connecting line produces can't read "cflist_top" Johannes Sixt
2012-10-04 20:50 ` Stefan Haller [this message]
2012-10-04 20:50 ` [PATCH 1/2] gitk: Fix error message when clicking on a connecting line Stefan Haller
2012-10-04 20:50 ` [PATCH 2/2] gitk: When searching, only highlight files when in Patch mode Stefan Haller
2012-10-21 22:25 ` [BUG] gitk: clicking on a connecting line produces can't read "cflist_top" Paul Mackerras
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).