From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: gitweb.cgi in C
Date: Thu, 8 Dec 2005 23:46:26 +0100 [thread overview]
Message-ID: <20051208224626.GP22159@pasky.or.cz> (raw)
In-Reply-To: <7vfyp3b4ki.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Thu, Dec 08, 2005 at 11:35:09PM CET, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> Petr Baudis <pasky@suse.cz> writes:
>
> > Dear diary, on Thu, Dec 08, 2005 at 07:59:37PM CET, I got a letter
> > where Majkls <majkls@tiscali.cz> said that...
> >> What do you think about gitweb.cgi in C?
> >
> > To add to the collective dismay - why bother?
>
> It _might_ make sense to do gitweb using libified git Smurf is
> working on, in order to reduce forks and execs, but that is
> mostly independent of rewriting that in C.
I'd see having Perl XS for libgit as something much more sensible. And
you could do cute porcelain stuff with that as well.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-12-08 22:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 18:59 gitweb.cgi in C Majkls
2005-12-08 18:55 ` Kay Sievers
2005-12-08 19:51 ` Johannes Schindelin
2005-12-08 19:46 ` Ryan Anderson
2005-12-08 22:27 ` Petr Baudis
2005-12-08 22:35 ` Junio C Hamano
2005-12-08 22:46 ` Petr Baudis [this message]
2005-12-09 0:42 ` Junio C Hamano
2005-12-09 4:42 ` Randal L. Schwartz
2005-12-09 7:33 ` Junio C Hamano
2005-12-08 22:48 ` Andreas Ericsson
2005-12-08 22:39 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 15:28 Mark Allen
2005-12-09 15:45 ` Randal L. Schwartz
2005-12-09 17:59 ` Junio C Hamano
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=20051208224626.GP22159@pasky.or.cz \
--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).