From: Andy Parkins <andyparkins@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-gui blame dividing by zero
Date: Wed, 4 Apr 2007 16:21:49 +0100 [thread overview]
Message-ID: <200704041621.51390.andyparkins@gmail.com> (raw)
Hello,
I've not used it before, but I thought I'd give it a go:
$ git --version
git version 1.5.1
$ $ git-gui --version
git-gui version 0.6.5
$ git-gui blame HEAD somefile.cc
I just get a window that contains:
divide by zero
divide by zero
while executing
"expr {100 * $blame_data($w,blame_lines)
/ $blame_data($w,total_lines)}"
(procedure "blame_incremental_status" line 4)
invoked from within
"blame_incremental_status $w"
(procedure "read_blame_catfile" line 27)
invoked from within
"read_blame_catfile file6 {} HEAD
somefile.cc .cm.t .out.loaded_t .out.linenumber_t .out.file_t"
Am I doing something wrong?
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next reply other threads:[~2007-04-04 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 15:21 Andy Parkins [this message]
2007-04-04 15:27 ` git-gui blame dividing by zero Shawn O. Pearce
2007-04-04 16:11 ` Shawn O. Pearce
2007-04-05 8:33 ` Andy Parkins
2007-04-05 8:44 ` Andy Parkins
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=200704041621.51390.andyparkins@gmail.com \
--to=andyparkins@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).