From: "Dongsheng Song" <dongsheng.song@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org, "Jakub Narebski" <jnareb@gmail.com>
Subject: Re: Why gitweb commitdiff NO diff output ?
Date: Sun, 8 Oct 2006 16:22:23 +0800 [thread overview]
Message-ID: <4b3406f0610080122r17a10ea4h2c71a399fb8398a@mail.gmail.com> (raw)
In-Reply-To: <7vwt7hnvsk.fsf@assigned-by-dhcp.cox.net>
> >> Not enough information.
There is gitweb address:
http://www.foresee.com.cn:8888/git/
bad output:
http://www.foresee.com.cn:8888/git/?p=gcc/.git;a=commitdiff;h=c977ee1b2e54d67bb379ce476f784431c32136d7
debian pkgs:
ii bash 3.1-5
The GNU Bourne Again SHell
ii cogito 0.17.3-2
version control system
ii diff 2.8.1-11
File comparison utilities
ii git-core 1.4.2.1-1
content addressable filesystem
ii git-cvs 1.4.2.1-1
content addressable filesystem (cvs interope
ii git-doc 1.4.2.1-1
content addressable filesystem (documentatio
ii git-email 1.4.2.1-1
content addressable filesystem (email add-on
ii git-svn 1.4.2.1-1
content addressable filesystem (svn interope
ii gitweb 1.4.2.1-1
content addressable filesystem (web interfac
ii kernel-image-2.4.27-2-686 2.4.27-12
Linux kernel image for version 2.4.27 on PPr
ii patch 2.5.9-4
Apply a diff file to an original
But the other debian 2.6.x kernel is OK!
next prev parent reply other threads:[~2006-10-08 8:22 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 [this message]
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
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=4b3406f0610080122r17a10ea4h2c71a399fb8398a@mail.gmail.com \
--to=dongsheng.song@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
/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).