Re: Why gitweb commitdiff NO diff output ?

From: Junio C Hamano <junkio@cox.net>
Date: Oct 10, 2006, 06:54 UTC
Message-ID: <7vy7ro64pq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <4b3406f0610092336v5ab58134i280f64223a272b0b@mail.gmail.com>

"Dongsheng Song" <dongsheng.song@gmail.com> writes:

Show 25 quoted lines

> There is the result:
>
> www-data@ab:/home/repository/git/gcc$ for blob in \
>>          a34d77e47bf1561db1ade4f6b247598b880f80d5 \
>>          7625c494df01d4745e67bd4423e2fdbe9fc43799 \
>>          b207fe30a5430f97d27d398d89c974b068694c7a \
>>          57b07ace4bb6352416bbf9436b9f2642b3273257
>>          do
>>                git cat-file -t $blob || echo $blob does not exist
>>          done
> blob
> blob
> blob
> blob
> www-data@ab:/home/repository/git/gcc$ git cat-file commit
> c977ee1b2e54d67bb379ce476f784431c32136d7 |
>>          grep 'parent '
> parent b693aceaba66f741cd6735d4ecd16fe59394a2cf
> www-data@ab:/home/repository/git/gcc$ git diff-tree -p
> c977ee1b2e54d67bb379ce476f784431c32136d7 | wc
>     37     137    1179
> ...
> I have the SAME problem with ALL commits,  ONLY the 2.4.x machine, but
> git-core/cg tools is OK. All git/cg/gitweb is good for other 2.6.x
> machines.

That's mildly interesting. I do not know the difference between your 2.4 and 2.6 machines (nor how many of each you have). I am guessing that either these machines are sharing one repository over NFS, or they have their own copies and none of them is corrupt (i.e. you got these reasonable results you pasted above from all of them).

At this point I have to say that this sounds like a problem that reproduces only for you on that particular machine. Maybe comparing the apache logs from a good machine and a bad one would tell you what's different between them?

I am not sure what version of gitweb your distribution packages, but it used to be that commitdiff page wanted to create temporary file somewhere on the filesystem (the variable was $git_temp and by default it was set to "/tmp/gitweb", I think). Your other pages such as commit and log page seem to be working, so perhaps your gitweb has trouble writing there only on that machine?