All of lore.kernel.org
 help / color / mirror / Atom feed
From: nadim khemir <nadim@khemir.net>
To: git@vger.kernel.org
Subject: Re: Git.pm
Date: Sun, 23 Nov 2008 21:09:01 +0100	[thread overview]
Message-ID: <200811232109.01436.nadim@khemir.net> (raw)
In-Reply-To: <m363mhlw92.fsf@localhost.localdomain>

On Friday 21 November 2008 03.56.51 Jakub Narebski wrote:
> Actually there are one and a half of Perl interfaces to Git: Git.pm
> created by Pasky (who, as far as I understand is not a Perl hacker)
> which is in git.git repository, and Git::Repo and friends created by
> Lea Wiemann during her work on "gitweb caching" project at Google
> Summer of Code 2008 (you can find her repository at git wiki page
> http://git.or.cz/gitwiki/SoC2008Projects).
>
>
> If I remember history of Git.pm correctly, it was first created as a
> way to collect together and uniquify various versions of safe_pipe and
> safe_qx which were used by various Perl scripts in git; something like
> Perl version of git-sh-setup.sh for shell scripts... At first it even
> used XS in parts, but the build system was deemed too unportable (it
> depended on -fPIC). One of design decisions was to use Error.pm for
> throwing errors; I'm not a Perl hacker, so I cannot say if this was a
> good decision, and if implementation of this part is good.

Using Error.pm is not a bad decision even if more simple mechanisms do the 
job.

> Lea Wiemann work on Git::Repo and friends was created as object
> oriented interface. It was build from ground up instead of reusing
> Git.pm to be not encumbered by Git.pm cruft... unfortunately it means
> also abandoning all the work that went in Git.pm to make it portable
> (read: make it work with crippled ActiveState Perl). You can find
> discussion on the design of Git::Repo and decision of it being clean
> state implementation at link given by Pasky.
>
> P.S. I have "[RFC] Git Perl bindings, and OO interface" half-written
> (well, more like a third), a bit stalled. I'll try to find time to
> finish it and send it to git mailing list.

That would be very usefull. the  relevant information should be integrated in 
the module itself.

Thank you for your input on the history of Git.pm.

Cheers, Nadim

  reply	other threads:[~2008-11-23 20:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:56 Git.pm nadim khemir
2008-11-20  8:34 ` Git.pm Petr Baudis
2008-11-20 13:07   ` Git.pm Petr Baudis
2008-11-23 19:58   ` Git.pm nadim khemir
2008-12-07 17:39     ` Git.pm nadim khemir
2008-11-21  2:56 ` Git.pm Jakub Narebski
2008-11-23 20:09   ` nadim khemir [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-26  4:15 Git.pm Subho Banerjee
2012-04-26 18:41 ` Git.pm Randal L. Schwartz
2012-04-26 18:58 ` Git.pm Tim Henigan
2012-04-26 20:10   ` Git.pm Subho Banerjee
2012-04-26 20:31     ` Git.pm Jonathan Nieder
2012-05-10 13:19       ` Git.pm Subho Banerjee
2012-05-10 15:16         ` Git.pm Jonathan Nieder
2012-05-10 15:54         ` Git.pm demerphq
2012-05-10 16:18           ` Git.pm Subho Banerjee
2012-05-10 17:22             ` Git.pm demerphq
2012-05-10 16:20           ` Git.pm Junio C Hamano
2012-05-10 17:38             ` Git.pm demerphq
2012-05-10 20:55         ` Git.pm Andrew Sayers
2012-05-11  8:27           ` Git.pm demerphq
2012-05-11 16:56         ` Git.pm Randal L. Schwartz
2012-05-11 18:10           ` Git.pm Junio C Hamano
2012-04-26 19:17 ` Git.pm Junio C Hamano
2012-04-26 19:59 ` Git.pm Sam Vilain

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=200811232109.01436.nadim@khemir.net \
    --to=nadim@khemir.net \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.