From: Jonathan Nieder <jrnieder@gmail.com>
To: Vicent Marti <tanoku@gmail.com>
Cc: libgit2@librelist.com, git@vger.kernel.org,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: Using libgit2 code in git.git as a Google Summer of Code project?
Date: Thu, 10 Mar 2011 05:55:49 -0600 [thread overview]
Message-ID: <20110310115549.GA31046@elie> (raw)
In-Reply-To: <AANLkTikQ3x9A6v3y698_om_4_qB87Zpi_kG3u3=d+Dur@mail.gmail.com>
Hi again,
Two quick notes.
Vicent Marti wrote:
> I think that right now it would be a quite daunting task to start
> replacing parts of git.git with libgit2. The architecture changes
> required would be quite significant, because of the way that git.git
> and libgit2 are designed (Unix-only, non-reentrant/cross-platform,
> reentrant)
(Side note: git actually can be built with MSVC, though the build
process might be unfamiliar. See compat/vcbuild/README for details.)
> On top of that, the API for the library is not
> yet stable, so that integration may end up being kind-of-wasted work.
This is precisely why I want to see attempts at using it starting
soon, whether as a student project or not: it would be a bad thing if
git reveals assumptions or limitations in the API requiring major
rework after the API has already solidified.
> So, personally, I don't know anybody interested on mentoring *that*
> specific task, but I'm certainly interested on mentoring a "help
> complete libgit2" task
Sounds good to me. ;-)
Thanks for explaining.
Jonathan
next prev parent reply other threads:[~2011-03-10 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinqem5e0+vxzR64s1Y9o7B8RgEFXcm0HV_jeZ4Y@mail.gmail.com>
[not found] ` <AANLkTikkFDLKn5KMaSTwUABBVX_vYDj8pW1kqmsm1_vy@mail.gmail.com>
2011-03-10 10:13 ` Using libgit2 code in git.git as a Google Summer of Code project? Jonathan Nieder
2011-03-10 10:18 ` Jonathan Nieder
2011-03-10 11:33 ` Vicent Marti
2011-03-10 11:39 ` Nguyen Thai Ngoc Duy
2011-03-10 12:56 ` Vicent Marti
2011-03-13 17:11 ` Ramkumar Ramachandra
2011-03-10 11:55 ` Jonathan Nieder [this message]
2011-03-10 19:27 ` Junio C Hamano
2011-03-11 12:22 ` Vicent Marti
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=20110310115549.GA31046@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=libgit2@librelist.com \
--cc=pclouds@gmail.com \
--cc=tanoku@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).