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:19:15 +0200 [thread overview]
Message-ID: <20061024191915.GV18879@pasky.or.cz> (raw)
In-Reply-To: <524029.7339.qm@web31812.mail.mud.yahoo.com>
On Tue, Oct 24, 2006 at 09:09:03PM CEST, Luben Tuikov wrote:
> --- Petr Baudis <pasky@suse.cz> wrote:
> > > Why not instead re-submit a patch implementing what was discussed
> > > in this thread bearing the same name:
> > >
> > > http://marc.theaimsgroup.com/?t=116044914900001&r=1&w=2
> >
> > This implements
> >
> > http://marc.theaimsgroup.com/?l=git&m=116047939517299&w=2
> >
> > I see no other ideas I could take there except various naming proposals
> > and perhaps using File::Copy but I'll wait until someone does a
> > gitweb-wide change for the latter.
> >
> > I don't really care _what_ name it bears, but I'd like to have it
> > included. :-)
>
> People have suggested that this functionality be folded into the
> "Description" column, where the description printed is the
> first line of the description file "description" and if clicked
> on, it shows the whole "descrption" file.
Please look at the mail the mail I referred was a reply to:
http://marc.theaimsgroup.com/?l=git&m=116047773825208&w=2
--
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
next prev parent reply other threads:[~2006-10-24 19:19 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 [this message]
2006-10-24 19:41 ` Luben Tuikov
2006-10-24 19:50 ` Petr Baudis
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=20061024191915.GV18879@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).