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: Tue, 10 Oct 2006 10:42:38 -0700 [thread overview]
Message-ID: <7viris2hkh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 4b3406f0610100346v16f1f2f6i305963bc1b398dac@mail.gmail.com
"Dongsheng Song" <dongsheng.song@gmail•com> writes:
> Thanks, now that's OK.
>
>> 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?
Care to share your experience to help others?
If it was /tmp/gitweb permission problem then the newer gitweb
shouldn't have that issue so it would be a moot point, but if
the pitfall still applies to the current software we might want
to add a "common pitfals" section to gitweb/README.
next prev parent reply other threads:[~2006-10-10 17:42 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
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 [this message]
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=7viris2hkh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=dongsheng.song@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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