git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Dongsheng Song" <dongsheng.song@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Why gitweb commitdiff NO diff output ?
Date: Mon, 09 Oct 2006 19:28:07 -0700	[thread overview]
Message-ID: <7viris9a6g.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v1wpgapew.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Mon, 09 Oct 2006 19:13:43 -0700")

Junio C Hamano <junkio@cox.net> writes:

> "Dongsheng Song" <dongsheng.song@gmail.com> writes:
>
>> NO.
>>
>> When I change the repository's owner to gitweb process,  no diff output yet.
>>
>> $ chown -R www-data:www-data  cauchy/ gcc/ mph/
>>
>> 2006/10/10, Junio C Hamano <junkio@cox.net>:
>>> The site does not return any of these four blobs that are part
>>> of the commitdiff when a=blob is requested on them.
>>>
>>>         file:a34d77e47bf1561db1ade4f6b247598b880f80d5 ->
>>>         file:7625c494df01d4745e67bd4423e2fdbe9fc43799
>>>
>>>         file:b207fe30a5430f97d27d398d89c974b068694c7a ->
>>>         file:57b07ace4bb6352416bbf9436b9f2642b3273257
>>>
>>> I would first suspect if the repository actually have them _and_
>>> with an appropriate mode protection to be readable by your
>>> gitweb process.
>
> And does the repository have these four blob objects?

Sorry, the follow-up question was not very helpful to guide
another person over e-mail.  Let's try again with more specific
questions.

What do these say in that repository when run as the webserver
user?

	$ for blob in \
          a34d77e47bf1561db1ade4f6b247598b880f80d5 \
	  7625c494df01d4745e67bd4423e2fdbe9fc43799 \
          b207fe30a5430f97d27d398d89c974b068694c7a \
          57b07ace4bb6352416bbf9436b9f2642b3273257
	  do
          	git cat-file -t $blob || echo $blob does not exist
	  done
	$ git cat-file commit c977ee1b2e54d67bb379ce476f784431c32136d7 |
	  grep 'parent '
	$ git diff-tree -p c977ee1b2e54d67bb379ce476f784431c32136d7 | wc

The first one tries to make sure you have those four blob
objects in the repository, the second tries to make sure the
commit is a single parent commit as your gitweb output suggests,
and the last one is to obtain the diff text.

Also do you have the same problem with other commits, or is this
the only commit your gitweb is having trouble with showing
commitdiff?

  reply	other threads:[~2006-10-10  2:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  7:32 Why gitweb commitdiff NO diff output ? Dongsheng Song
2006-10-03  9:02 ` Jakub Narebski
2006-10-03  9:52   ` Martin Waitz
2006-10-03 17:39     ` Junio C Hamano
2006-10-08  8:22       ` Dongsheng Song
2006-10-10  0:32         ` Junio C Hamano
2006-10-10  1:51           ` Dongsheng Song
2006-10-10  2:13             ` Junio C Hamano
2006-10-10  2:28               ` Junio C Hamano [this message]
2006-10-10  6:36                 ` Dongsheng Song
2006-10-10  6:54                   ` Junio C Hamano
2006-10-10 10:46                     ` Dongsheng Song
2006-10-10 17:42                       ` Junio C Hamano
2006-10-10 19:01                         ` Johannes Schindelin
2006-10-11  2:31                         ` Dongsheng Song

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=7viris9a6g.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=dongsheng.song@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).