From: Petr Baudis <pasky@suse.cz>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Show project's README.html if available
Date: Tue, 24 Oct 2006 21:50:35 +0200 [thread overview]
Message-ID: <20061024195035.GH20017@pasky.or.cz> (raw)
In-Reply-To: <701637.67420.qm@web31802.mail.mud.yahoo.com>
Dear diary, on Tue, Oct 24, 2006 at 09:41:04PM CEST, I got a letter
where Luben Tuikov <ltuikov@yahoo.com> said that...
> I re-read that email. And I also saw what you have at hed.git.
>
> If anything I think we should want to _minimize_ shown material
> before the "shortlog" in the "summary" page.
>
> Why?
>
> Well, in a production environment, people often view the "summary" page
> to see what has been going on with a project and they are well aware
> of what that project is for and/or what it does. It is cumbersome to have
> to scroll down each and every time past he annoying "readme", just to see
> the first few commits.
Yes, I agree that this is valid concern. I've been thinking about
showing readme in parallel with the summary box, do people think that
would fix the issue?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
prev parent reply other threads:[~2006-10-24 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 3:23 [PATCH] gitweb: Show project's README.html if available Petr Baudis
2006-10-24 8:43 ` Luben Tuikov
2006-10-24 11:30 ` Petr Baudis
2006-10-24 19:09 ` Luben Tuikov
2006-10-24 19:19 ` Petr Baudis
2006-10-24 19:41 ` Luben Tuikov
2006-10-24 19:50 ` Petr Baudis [this message]
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=20061024195035.GH20017@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ltuikov@yahoo.com \
/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).