From: Petr Baudis Date: Tue, 10 Oct 2006 10:55:21 GMT Subject: Re: [PATCH] gitweb: Show project README if available Message-ID: <20061010105521.GQ20017@pasky.or.cz> In-Reply-To: <7v7iz894ct.fsf@assigned-by-dhcp.cox.net> Dear diary, on Tue, Oct 10, 2006 at 06:33:54AM CEST, I got a letter where Junio C Hamano said that... > Junio C Hamano writes: > > > Petr Baudis writes: > > > >> If the project includes a README file, show it in the summary page. > >... > > I wonder how this should relate to .git/description file, > > though. In other words, it _might_ make sense to change where > > we show the contents of description right now to show the first > > line and take README from the same location. In principle I like this idea. One problem is that description is not supposed to contain HTML and my README is (perhaps it should read README.html instead), and I really want README to. And if it's not plaintext, division of the first line and the rest does not work so well: If you show first line of description as the "short" one and whole description as the "full" one in summary page, it will look awkward. If you look at http://repo.or.cz/gitweb.cgi/hed.git, the first line in the full description starts with boldened Hed, and is of course a separate paragraph etc. > Also we might want to consider using this file (or description) > for git-daemon "motd" action if we were to enhance it. I > remember that early days of git-daemon some people wanted to > have motd. I'd rather keep those separate... -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i