From: Mark Levedahl <mlevedahl@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk - error in git repo on cygwin
Date: Wed, 04 Jul 2007 21:58:33 -0400 [thread overview]
Message-ID: <468C5049.9040403@gmail.com> (raw)
In-Reply-To: <18060.12148.313090.53861@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> I don't think anything like that has changed. I think it is probably
> due to the commits being batched up differently in getcommitlines.
> I'll look into it.
>
> Paul.
>
>
Indeed, it does seem to be something order dependent. I added some debug
printouts, and looking in proc "rowranges" when the error occurs (for
gitk f77a29e), I get:
$commitrow($curview,$id) = 8571
[lindex $rowrangelist $commitrow($curview,$id)] =
29504118f8528f658fd0bfc02d8d78d4c01dc2cc 8571
In all previous cases, the lindex expression evalutates to two sha1's.
So clearly, the order of processing is different. I did check that the
input (from git-rev-list) is identical across the linux and Cygwin
invocations. Shrug.
Mark
prev parent reply other threads:[~2007-07-05 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 13:33 gitk - error in git repo on cygwin Mark Levedahl
2007-07-04 23:38 ` Paul Mackerras
2007-07-05 1:58 ` Mark Levedahl [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=468C5049.9040403@gmail.com \
--to=mlevedahl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.