git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: gitk - error in git repo on cygwin

From
Mark Levedahl <mlevedahl@gmail.com>
Date
Jul 5, 2007, 01:58 UTC
Message-ID
<468C5049.9040403@gmail.com>
In-Reply-To
<18060.12148.313090.53861@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
Show 7 quoted lines
> 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
Previous: Paul Mackerras
Message 3 of 3 in “gitk - error in git repo on cygwin”
  1. Mark LevedahlJul 4, 2007
  2. Paul MackerrasJul 4, 2007
  3. Mark LevedahlJul 5, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.