git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Dennis Stosberg <dennis@stosberg.net>
Cc: Junio C Hamano <junkio@cox.net>, pasky@suse.cz, git@vger.kernel.org
Subject: Re: Dropping Git.pm (at least Git.xs)?
Date: Mon, 11 Sep 2006 05:59:54 +1200	[thread overview]
Message-ID: <4504529A.70401@vilain.net> (raw)
In-Reply-To: <20060903150305.G50c94aea@leonov.stosberg.net>

Dennis Stosberg wrote:
> Having perl bindings to git internals and sometime in the future to a
> libified git is a great thing.  It will allow people to do interesting
> things, quickly trying concepts without having to write any C code.
> And I expect that gitweb can be sped up remarkably by using Git.pm (no
> forking, parsing of command output often not necessary, easy caching of
> frequently cached data across calls, etc)

FWIW, I have been starting on a perl implementation.  It uses the
Git.pm, but not for anything *that* important.  It's still very young,
but once I have reading and writing files basically working, I'll
release it to CPAN separately - no reason it needs to be distributed
with Git itself.

See http://utsl.gen.nz/gitweb/?p=VCS-Git

I used this design to talk about Moose at YAPC::Europe 2006.
http://utsl.gen.nz/talks/moose/start.html

Sam.

  reply	other threads:[~2006-09-10 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 11:34 Dropping Git.pm (at least Git.xs)? Junio C Hamano
2006-09-03 15:03 ` Dennis Stosberg
2006-09-10 17:59   ` Sam Vilain [this message]
2006-09-10 22:13     ` Jakub Narebski
2006-09-11  3:25     ` Petr Baudis
2006-09-11  8:58       ` Jakub Narebski
2006-09-07 19:51 ` 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=4504529A.70401@vilain.net \
    --to=sam@vilain.net \
    --cc=dennis@stosberg.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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).