Re: [PATCH 2/2] Move sequencer to builtin

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Jun 9, 2013, 18:07 UTC
Message-ID: <CAMP44s2umN3prdPnb=kuvH4OrQqcKDyu8ExfkXHAR2nC=a6weA@mail.gmail.com>
In-Reply-To: <20130609175554.GA810@sigill.intra.peff.net>

On Sun, Jun 9, 2013 at 12:55 PM, Jeff King <peff@peff.net> wrote:

Show 16 quoted lines

> On Sun, Jun 09, 2013 at 03:28:48PM +0530, Ramkumar Ramachandra wrote:
>
>> Jeff King wrote:
>> > Sorry that I cannot show you the source code, but you may interested to
>> > know that libgit2 powers:
>>
>> Yes, I'm well aware of these: libgit2 is LGPL, because of which these
>> three proprietary applications have been made possible.  Isn't it
>> completely orthogonal to the discussion about how best to lib'ify
>> git.git though?  From what I understand, fc is not interested in
>> building another application leveraging libgit.a or libgit2; he's
>> interested in improving libgit.a and getting more users.
>
> Perhaps I misunderstood the discussion, but it looked to me that there
> was an assertion that libgit2 was not ready for useful work. I do not
> think that is true, and I tried to counter it with facts.

That was not the point. Take 'contrib/related/git-related', or any useful script, and make it so it uses libgit2 instead of forking 'git foo' commands.

It's not going to happen.

-- 
Felipe Contreras