From: nadim khemir <nadim@khemir.net>
To: git@vger.kernel.org
Subject: Re: [RFC] Git Perl bindings, and OO interface
Date: Sun, 30 Nov 2008 14:45:18 +0100 [thread overview]
Message-ID: <200811301445.18969.nadim@khemir.net> (raw)
In-Reply-To: <200811270258.50898.jnareb@gmail.com>
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?
Nadim.
next prev parent reply other threads:[~2008-11-30 13:45 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 [this message]
2008-11-30 14:50 ` Jakub Narebski
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=200811301445.18969.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 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).