From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Show project README if available
Date: Tue, 10 Oct 2006 13:21:17 +0200 [thread overview]
Message-ID: <egfvlb$m2c$1@sea.gmane.org> (raw)
In-Reply-To: 20061010105521.GQ20017@pasky.or.cz
Petr Baudis wrote:
> Dear diary, on Tue, Oct 10, 2006 at 06:33:54AM CEST, I got a letter
> where Junio C Hamano <junkio@cox.net> said that...
>> Junio C Hamano <junkio@cox.net> writes:
>>
>> > Petr Baudis <pasky@suse.cz> 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:
Perhaps we should assume $GIT_DIR/README to be text/plain (and useable
as motd), and $GIT_DIR/README.html as text/html, preffering the README.html.
The "problem" is if README.html is HTML _fragment_, or is it self contained
HTML (and we should use iframe, object, or strip it).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-10 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 2:56 [PATCH] gitweb: Show project README if available Petr Baudis
2006-10-10 3:20 ` 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 [this message]
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='egfvlb$m2c$1@sea.gmane.org' \
--to=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.