From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: <git@vger.kernel.org>
Subject: [PATCH] gitweb: Show project README if available
Date: Tue, 10 Oct 2006 04:56:28 +0200 [thread overview]
Message-ID: <20061010025627.19317.70511.stgit@rover> (raw)
If the project includes a README file, show it in the summary page.
The usual "this should be in the config file" argument does not apply here
since this can be larger and having such a big string in the config file
would be impractical.
I don't know if this is suitable upstream, but it's one of the repo.or.cz
custom modifications that I've thought could be interesting for others
as well.
Signed-off-by: Petr Baudis <pasky@suse.cz>
---
gitweb/gitweb.perl | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 7547c4d..4e56af9 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -2535,6 +2535,14 @@ sub git_summary {
}
print "</table>\n";
+ if (-s "$projectroot/$project/README") {
+ if (open my $fd, "$projectroot/$project/README") {
+ print "<div class=\"title\">readme</div>\n";
+ print $_ while (<$fd>);
+ close $fd;
+ }
+ }
+
open my $fd, "-|", git_cmd(), "rev-list", "--max-count=17",
git_get_head_hash($project)
or die_error(undef, "Open git-rev-list failed");
next reply other threads:[~2006-10-10 2:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 2:56 Petr Baudis [this message]
2006-10-10 3:20 ` [PATCH] gitweb: Show project README if available Junio C Hamano
2006-10-10 4:33 ` Junio C Hamano
2006-10-10 10:55 ` Petr Baudis
2006-10-10 11:21 ` Jakub Narebski
2006-10-10 14:25 ` Horst H. von Brand
2006-10-10 5:15 ` Luben Tuikov
2006-10-10 8:33 ` Andreas Ericsson
2006-10-10 9:00 ` Jakub Narebski
2006-10-10 10:41 ` Petr Baudis
2006-10-11 12:23 ` Jakub Narebski
2006-10-11 18:17 ` Jeff King
2006-10-11 18:46 ` Jakub Narebski
2006-10-11 19:32 ` Junio C Hamano
2006-10-11 20:33 ` Jakub Narebski
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=20061010025627.19317.70511.stgit@rover \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--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).