All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: nadim khemir <nadim@khemir.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git Perl bindings, and OO interface
Date: Sun, 30 Nov 2008 06:50:38 -0800 (PST)	[thread overview]
Message-ID: <m37i6ljmjy.fsf@localhost.localdomain> (raw)
In-Reply-To: <200811301445.18969.nadim@khemir.net>

nadim khemir <nadim@khemir.net> writes:
> On Thursday 27 November 2008 02.58.49 Jakub Narebski wrote:
> > ...
> >
> > 7. Git::Refs
> >
> >    It is meant to represent references, mainly branches, and be filled
> >    using git-for-each-ref... and for example used for ref markers.
> >
> > There are probably a few things I have forgot about...
> 
> Thank you for writing the RFC, it's a very good start. I would like to see 
> some strategy for libgit[2] in the RFC. What is your opinion about that?

I do not know enought about libgit2 or even git unofficial internal C
API to talk about it.

I did not plan for Perl interface to be actual Perl bindings, using
libgit2.  Please remember that earlier effort of using XS (Perl <-> C
interface) failed because it relied on GCC support for -fPIC and was
not sufficiently portable... if I remember it correctly.  Calling Git
commands and massaging output would be enough for me.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-11-30 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  1:58 [RFC] Git Perl bindings, and OO interface Jakub Narebski
2008-11-30 13:45 ` nadim khemir
2008-11-30 14:50   ` Jakub Narebski [this message]
2009-07-10  2:08 ` Tom Lanyon

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=m37i6ljmjy.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nadim@khemir.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 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.