From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Mark Allen <mrallen1@yahoo.com>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: gitweb.cgi in C
Date: 09 Dec 2005 07:45:57 -0800 [thread overview]
Message-ID: <86r78m8ea2.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051209152847.28358.qmail@web34310.mail.mud.yahoo.com>
>>>>> "Mark" == Mark Allen <mrallen1@yahoo.com> writes:
Mark> I started working on a GIT-XS project around GIT 0.9 timeframe, but the changes to APIs
Mark> and calls was still way too rapid, so I decided to back burner it.
Mark> I haven't looked at the libification work that Smurf is doing (haven't made time for it
Mark> lately), but if it's not 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.
I spent about ten minutes trying to find this information a few weeks
back, but apparently, that was about five minutes (or more) too short.
Any quick pointers on how -lgit is constructed?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-12-09 15:46 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 [this message]
2005-12-09 17:59 ` Junio C Hamano
-- 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=86r78m8ea2.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).