From: Christian Couder <chriscool@tuxfamily.org>
To: "Scott Chacon" <schacon@gmail.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: GitTogether topics status
Date: Fri, 19 Sep 2008 08:35:54 +0200 [thread overview]
Message-ID: <200809190835.55103.chriscool@tuxfamily.org> (raw)
In-Reply-To: <d411cc4a0809182303x365e2280r3fc8a9a3534d8890@mail.gmail.com>
Le vendredi 19 septembre 2008, Scott Chacon a écrit :
> Hi,
>
> On Thu, Sep 18, 2008 at 10:03 PM, Christian Couder
>
> <chriscool@tuxfamily.org> wrote:
> > Le jeudi 18 septembre 2008, Jakub Narebski a écrit :
> >
> >> What also might be interesting to talk about scriptability, having
> >> defined API, libification (I see that there is planned), interfaces to
> >> other programming languages versus calling git plumbing versus
> >> reimplementing git in other languages (e.g. JGit vs JavaGit, Grit vs
> >> Ruby/Git, GitPython vs PyGit, Git.pm vs Git::Repo), but I guess this
> >> discussion could be had on git mailing list.
> >
> > The following topics are now together on the wiki:
> >
> > * Linkable library for basic object access (libification or new
> > library) * Scriptability, using git in other languages (using
> > interfaces vs calling plumbing vs reimplementting)
> >
> > The second one is new.
> >
> > If we want these topics to be discussed during the GitTogether, we need
> > someone who wants to talk about or at least introduce these subjects
> > though. (Hint, hint.)
>
> I would be happy to talk about / introduce at least the second one,
> since I've done most of the work on the pure-ruby implementation of
> git in the Grit project, which is one of the more popular of the
> re-implementations out there (and runs the GitHub site). I would also
> be happy to help with a discussion on the first one, since I added it
> to the wiki in the first place and it is heavily connected to the
> second topic. I very much want to see a library that provides basic
> Git object access that we can use to write proper bindings in
> Ruby/Python/Perl. If the current Git code is too difficult to libify
> properly, then perhaps an alternate C implementation that is built
> only for that purpose is preferable to having a re-implementation in
> _every_ language. Looking forward to the discussion.
Great! You are now in the "Possible speakers" list on the wiki.
Thanks,
Christian.
next prev parent reply other threads:[~2008-09-19 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 20:07 GitTogether topics status Christian Couder
2008-09-18 20:48 ` Jakub Narebski
2008-09-19 5:03 ` Christian Couder
2008-09-19 6:03 ` Scott Chacon
2008-09-19 6:35 ` Christian Couder [this message]
2008-09-19 10:11 ` Johannes Schindelin
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=200809190835.55103.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=schacon@gmail.com \
--cc=spearce@spearce.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