From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz),
Mark Allen <mrallen1@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb.cgi in C
Date: Fri, 09 Dec 2005 09:59:38 -0800 [thread overview]
Message-ID: <7vhd9i40dx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86r78m8ea2.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "09 Dec 2005 07:45:57 -0800")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
>>>>>> "Mark" == Mark Allen <mrallen1@yahoo.com> writes:
> Mark> I haven't looked at the libification work that Smurf is
> Mark> doing (haven't made time for it lately), but if it's not
> Mark> TOO python specific, maybe I can use it too.
> A "lite" version using Inline::C can be quickly constructed if
> only the API were all listed in one place, or a few easy to find places.
Guys, the "libificiation work" is more than that, and the more
important and bigger task is not the part you connect libgit to
your favorite P* languages, but first the part to reorganize
libgit to be usable in that form.
I've outlined what needs to be done a couple of months ago:
http://marc.theaimsgroup.com/?t=112687447700001
next prev parent reply other threads:[~2005-12-09 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 15:28 gitweb.cgi in C Mark Allen
2005-12-09 15:45 ` Randal L. Schwartz
2005-12-09 17:59 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 18:59 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
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
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=7vhd9i40dx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=mrallen1@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).