From: David Barr <davidbarr@google.com>
To: Scott Chacon <schacon@gmail.com>
Cc: Brian Gernhardt <benji@silverinsanity.com>,
david@lang.hm, Ramkumar Ramachandra <artagnon@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [linux.conf.au] VCS Interoperability
Date: Fri, 27 Jan 2012 10:47:08 +1100 [thread overview]
Message-ID: <CAFfmPPPvpbsYz9cjN6OspivCN3dbuPGOU7fyaVdnic3D4V855w@mail.gmail.com> (raw)
In-Reply-To: <CAP2yMaLHK2md=MHFmV--R6rmr4q3XuZxqsb2fUszMhssx3GDoA@mail.gmail.com>
>>>> 3. What are your thoughts on lib'ifying Git so that others can call
>>>> into it using an API?
>>>
>>> This is something that everyone agrees would be a good thing. There have been many people who have started projects to do so, but they have all stalled.
>>
>> I believe libgit2 is still under active development.
>>
>> http://libgit2.github.com
>>
>
> Yes, GitHub alone actually has 2 full time employees and 1 contractor
> who are entirely dedicated to the project. It also ships with the
> GitHub for Mac product, so it's used in production by tens of
> thousands every day. If any of you want to get involved, you can check
> out the mailing list (libgit2@librelist.org) or (probably more
> usefully) the GitHub project page:
>
> https://github.com/libgit2/libgit2
>
> Open tickets, contribute code, review PRs, etc.
I'm thinking libgit2 is where git features that have stablised are formalised.
On the other hand, git-core is where features are incubated.
I would like to see fast-import ported to libgit2 when it stabilises ;)
After giving my talk, I feel compelled to reroll the historic vcs-svn series.
I'm pushing as I go to my GitHub account:
https://github.com/barrbrain/git/commits/svn-fe-reroll
--
David Barr
next prev parent reply other threads:[~2012-01-26 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 12:30 [linux.conf.au] VCS Interoperability David Michael Barr
2012-01-10 8:48 ` Ramkumar Ramachandra
2012-01-22 3:39 ` David Michael Barr
2012-01-22 10:25 ` Ramkumar Ramachandra
2012-01-22 21:12 ` david
2012-01-22 23:33 ` Brian Gernhardt
2012-01-23 0:43 ` Scott Chacon
2012-01-26 23:47 ` David Barr [this message]
2012-01-27 0:10 ` Jonathan Nieder
2012-01-27 0:33 ` [PULL] svn-fe updates for master or next Jonathan Nieder
2012-01-27 0:46 ` Jonathan Nieder
2012-01-27 1:03 ` David Barr
2012-01-27 7:20 ` Jonathan Nieder
2012-01-27 18:39 ` Junio C Hamano
2012-01-28 4:37 ` Junio C Hamano
2012-01-27 18:50 ` Junio C Hamano
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=CAFfmPPPvpbsYz9cjN6OspivCN3dbuPGOU7fyaVdnic3D4V855w@mail.gmail.com \
--to=davidbarr@google.com \
--cc=artagnon@gmail.com \
--cc=benji@silverinsanity.com \
--cc=david@lang.hm \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=schacon@gmail.com \
/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).